Datagrounds BetaThe PUBG Mobile esports archive by The Dew Lab

NinjaBoi's 54 Finishes in 18 Upper Bracket Maps

A mobile esports competitor seen from behind at a dark desk in a green-lit arena

Why did NinjaBoi's BGMI performance at BMSD 2026 deserve attention, and how much of it came from the Upper Bracket? He led that stage with 54 finishes in 18 maps, averaging 3.00 per map for Team Outrage.

I'd call those 3 days his strongest stretch of the tournament. He supplied 43.9% of Outrage's Upper Bracket finishes, then finished the whole event with 141 in 70 maps. The later stages give that peak an important boundary.

NinjaBoi's BGMI Team

NinjaBoi played BMSD 2026 for Team Outrage. Liquipedia dates the event from September 22 to October 18, with the Upper Bracket held from October 1 to 3.

Liquipedia's BMSD roster lists the playing lineup as:

  • Omega
  • Slug
  • NinjaBoi
  • Knight

Amit is listed as coach and a non-playing reserve. Those are the event's roster details; they don't establish where anyone will play after a transfer window.

For the wider qualification route, I'd start with how the BGMI esports season works.

BMSD Upper Bracket Stats

In Liquipedia's Upper Bracket finish table, NinjaBoi led Phoenix by 8. Both played 18 maps, making this a useful comparison within the same lobby.

The leading rows in Liquipedia's player statistics, also recorded in Datagrounds, were:

Player

Team

Maps

Finishes

Finishes Per Map

NinjaBoi

Team Outrage

18

54

3.00

Phoenix

Nebula Esports

18

46

2.56

Knight

Team Outrage

18

36

2.00

KRATOS

Nebula Esports

18

33

1.83

JDGamingYT

Learn From Past

18

33

1.83

The team share gives 54 its scale. Outrage recorded 123 finishes, so 54 divided by 123 equals 43.9%. Almost half of the team's credited finishes came from NinjaBoi.

Knight added 36, putting the pair on 90 of 123 finishes, or 73.2%. I'd read that as concentrated finishing output, with the other players' value still requiring context beyond a finish count.

Team Outrage's Upper Bracket Result

Outrage finished 2nd behind Nebula despite recording more finishes. Placement points explain the gap in the Upper Bracket results.

Team

Chicken Dinners

Finishes

Placement Points

Total Points

Nebula Esports

5

119

59

178

Team Outrage

1

123

42

165

Outrage had 4 more finishes but 17 fewer placement points. That left them 13 points behind Nebula across the same 18 maps.

NinjaBoi's output helped Outrage lead the lobby in finishes. Nebula converted more matches into wins and earned the stronger placement return. I'd keep both measures in view when judging who had the better stage.

The Upper Bracket sent its top 8 directly to the Semi Finals. Outrage's 2nd place cleared that cut and avoided the Lower Bracket, where the remaining 8 teams had to continue.

NinjaBoi's BMSD Stage Split

The Upper Bracket was NinjaBoi's highest finish rate at BMSD. His other stages sat below 2 finishes per map, according to Datagrounds' BMSD record.

Stage

Maps

Finishes

Finishes Per Map

Share of Team Finishes

Qualifiers

18

34

1.89

35.8%

Upper Bracket

18

54

3.00

43.9%

Semi Finals

16

27

1.69

33.8%

Grand Finals

18

26

1.44

29.9%

Overall

70

141

2.01

36.6%

The overall row already includes the stages above it. The reconciliation is:

  • Finishes: 34 + 54 + 27 + 26 = 141
  • Maps: 18 + 18 + 16 + 18 = 70
  • Outside the Upper Bracket: 87 finishes in 52 maps, or 1.67 per map

He produced 38.3% of his event finishes in 25.7% of his maps. That concentration is why I'd give the Upper Bracket more attention than his overall average alone.

The Grand Finals had the same 18-map length and yielded 28 fewer individual finishes. Outrage's team finishes also fell, from 123 to 87, while NinjaBoi's share dropped to 29.9%.

Those numbers establish a smaller finishing contribution in the final. They don't explain the cause; opponents and match situations changed between stages.

NinjaBoi still placed 2nd by overall finishes. Taurus06 led with 149 in 86 recorded player maps, compared with NinjaBoi's 141 in 70.

That is an 8-finish lead across 16 more maps. I'd use Taurus's BMSD profile for the longer route, while keeping the different stage exposure beside any rate comparison.

Team Outrage's Grand Finals Finish

Outrage left BMSD with a BMIC seat. PCQuest's final standings put them 6th on 123 points, just 1 above Blue Army.

Their final comprised:

  • 87 finish points
  • 36 placement points
  • 123 total points across 18 maps

NinjaBoi contributed 26 of those finishes. His Upper Bracket peak hadn't carried through at the same rate, but his finals finishes still counted toward a qualification decided by 1 point.

I'd avoid assigning that seat to any single elimination. A margin that small depends on the team's entire final, including the placement points.

FAQs on NinjaBoi at BMSD 2026

Is NinjaBoi's 3.00 finishes per map the same as K/D?

No. Finishes per map divides credited finishes by maps played. K/D uses deaths as its denominator. The BMSD finish table does not provide a death count, so 3.00 should not be labeled his K/D.

Was NinjaBoi the BMSD 2026 Tournament MVP?

No. PCQuest lists Shubh of 8Bit as Tournament MVP and LEGIT of Team SouL as Finals MVP. Leading the Upper Bracket finish table was a separate statistical result.

Does a high finish share prove NinjaBoi was the entry player?

A finish share cannot establish who entered fights first or created the opening knocks. It measures credited finishes within the team. A tactical role claim would need separate evidence.

Can I compare these numbers with my ranked BGMI stats?

I'd keep them separate. These figures cover named BMSD tournament stages and their particular opponents. A ranked average comes from a different match sample and cannot establish an equivalent competitive level.

What I'd Watch Next

I'd watch whether NinjaBoi can sustain a larger share of Outrage's finishes through another complete final. Another strong qualifier would add less to his profile than carrying that output into the deciding stage.

My comparison would start with the other players in that same lobby, using equal map counts wherever possible. That would make the next standout run easier to judge without turning 1 exceptional stage into a career label.