Replay data updated 14 Oct 2026, 08:05 UTC · Daily update starts 01:00 UTC (03:00 Stockholm time)

Data updated 14 Oct, 08:05 UTC

Daily update starts 01:00 UTC (03:00 Stockholm time). Replay collection continues while the update is prepared.

‹ Find another player

bra1n5torm

Account 597516 · Published replay history across maps and positions.

Latest recorded OS
8.4
08 Aug 2026 · Large teams · 16 players
Recorded games
66
27 Jun 2026–08 Aug 2026 UTC
Maps played
9
Map versions counted separately
Compare with another player

OS over time

Ratings recorded at game start in the replays we have. OS means OpenSkill rating.

Large teams · 16 players

First recorded
6.45
Latest recorded
8.40
Change
+1.95
OS over timeRecorded ratings at game start. Use the game selector below to read individual values.2.54.76.99.111.327 Jun 2026, 14:49 UTC · OS 6.4528 Jun 2026, 23:53 UTC · OS 6.4629 Jun 2026, 00:12 UTC · OS 6.4629 Jun 2026, 01:22 UTC · OS 6.4629 Jun 2026, 02:57 UTC · OS 6.1429 Jun 2026, 21:14 UTC · OS 5.3429 Jun 2026, 21:37 UTC · OS 4.6429 Jun 2026, 22:02 UTC · OS 5.5530 Jun 2026, 00:41 UTC · OS 6.0901 Jul 2026, 22:15 UTC · OS 4.4702 Jul 2026, 01:37 UTC · OS 3.7302 Jul 2026, 23:26 UTC · OS 3.6305 Jul 2026, 01:28 UTC · OS 3.8405 Jul 2026, 02:46 UTC · OS 3.8405 Jul 2026, 15:17 UTC · OS 4.5607 Jul 2026, 23:06 UTC · OS 4.8808 Jul 2026, 00:13 UTC · OS 5.4008 Jul 2026, 00:37 UTC · OS 5.4008 Jul 2026, 01:05 UTC · OS 4.2108 Jul 2026, 01:28 UTC · OS 4.2108 Jul 2026, 01:50 UTC · OS 4.2109 Jul 2026, 02:40 UTC · OS 5.2812 Jul 2026, 16:24 UTC · OS 6.1412 Jul 2026, 21:18 UTC · OS 5.1913 Jul 2026, 20:56 UTC · OS 4.1413 Jul 2026, 21:16 UTC · OS 4.1413 Jul 2026, 22:35 UTC · OS 4.3514 Jul 2026, 01:36 UTC · OS 4.6515 Jul 2026, 23:28 UTC · OS 4.2515 Jul 2026, 23:50 UTC · OS 4.2516 Jul 2026, 01:50 UTC · OS 4.8717 Jul 2026, 00:07 UTC · OS 5.2717 Jul 2026, 00:51 UTC · OS 5.2717 Jul 2026, 01:09 UTC · OS 5.2718 Jul 2026, 01:00 UTC · OS 6.0219 Jul 2026, 01:20 UTC · OS 6.4419 Jul 2026, 13:15 UTC · OS 5.9619 Jul 2026, 13:43 UTC · OS 5.9619 Jul 2026, 23:39 UTC · OS 5.2121 Jul 2026, 01:22 UTC · OS 5.9421 Jul 2026, 21:13 UTC · OS 5.8121 Jul 2026, 21:26 UTC · OS 5.8122 Jul 2026, 02:07 UTC · OS 5.7922 Jul 2026, 02:31 UTC · OS 5.7922 Jul 2026, 02:50 UTC · OS 5.7922 Jul 2026, 03:09 UTC · OS 5.7922 Jul 2026, 18:02 UTC · OS 7.0223 Jul 2026, 21:18 UTC · OS 8.6823 Jul 2026, 21:36 UTC · OS 8.6824 Jul 2026, 00:04 UTC · OS 9.0224 Jul 2026, 22:19 UTC · OS 8.7030 Jul 2026, 02:01 UTC · OS 9.3531 Jul 2026, 00:08 UTC · OS 9.0331 Jul 2026, 00:25 UTC · OS 9.0301 Aug 2026, 02:50 UTC · OS 9.1002 Aug 2026, 15:02 UTC · OS 9.5802 Aug 2026, 22:58 UTC · OS 9.9802 Aug 2026, 23:39 UTC · OS 9.9803 Aug 2026, 00:01 UTC · OS 9.9804 Aug 2026, 01:42 UTC · OS 10.1604 Aug 2026, 23:28 UTC · OS 9.7605 Aug 2026, 22:55 UTC · OS 9.3305 Aug 2026, 23:15 UTC · OS 9.3307 Aug 2026, 01:48 UTC · OS 9.0507 Aug 2026, 02:20 UTC · OS 9.0508 Aug 2026, 00:22 UTC · OS 8.4027 Jun08 Aug

08 Aug 2026, 00:22 UTC · OS 8.40

66 recorded ratings · 27 Jun 2026–08 Aug 2026.

Playstyle and score by position

The same prepared traits shown in the BAR Fight widget. Each position keeps its own history; a trait describes a repeated habit, not a skill rating or the right choice in every game.

No habits to show yet. Habits come from Supreme Isthmus v2.1 human 8v8 games between 15 Sep and 14 Oct 2026 (UTC), with at least 10 measured games in a position. This player has none in that period.

Recent activity

Recorded games in the last four weeks. This shows activity, not a change in skill. Imports may be incomplete.

02026-09-17
to 2026-09-23
02026-09-24
to 2026-09-30
02026-10-01
to 2026-10-07
02026-10-08
to 2026-10-14

Most played maps & positions

Share of this player’s published games. Starting positions describe where they began; responsibilities can change during play.

All That Glitters v2.2.3

10 games
15.2% of recorded games

Unit-event data available: 100.0%.

Starting-lane opponents

Supreme Isthmus v2.1 human 8v8 starting lanes. This shows fixed opposing starts, not every opponent who later joined a fight.

See lane matchups and coverage

Starting-lane coverage: 38.8% of selected games.

Selected games: 49 · Games with identified lanes: 19.

25 distinct recorded opponents · Mean opponent OS 20.9 (OS available in 100.0% of identified games).

Beach sea vs Geo sea

9 matched games · 9 distinct opponents · Mean opponent OS 25.1.

Average economy and combat

Both sides use the same measured games for each row. Coverage is the share of games reaching that time with both measurements. Activity is against all enemies, not damage or spending against this lane opponent alone.

9 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponentCoverage
Metal producedTotal metal produced by this player by this time.2,941.1 metal3,753.2 metal100.0%9 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,611.8 metal4,616.4 metal100.0%9 paired games
Energy producedTotal energy produced by this player by this time.37,353.0 energy50,964.5 energy100.0%9 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.730.0 damage228.4 damage100.0%9 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.348.8 damage749.5 damage100.0%9 paired games
Units producedTotal units produced by this time, including buildings.26.4 units45.3 units100.0%9 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.0%0 paired games
Metal lost to enemiesMetal cost of completed units and buildings lost to enemies by this time. Includes commanders; excludes unfinished units and reclaim. Wreckage recovered later is not subtracted.Not recordedNot recorded0.0%0 paired games
Enemy metal destroyedMetal cost of completed enemy units and buildings credited to this player for their destruction. Aircraft crashes can credit the last attacker. Includes commanders; excludes unfinished units. Assists are not counted.Not recordedNot recorded0.0%0 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.Not recordedNot recorded0.0%0 paired games
  • [Crd]Claps1 game · 11.1% of games in this matchup · Mean recorded OS 31.4Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Afganski_Rzeznik1 game · 11.1% of games in this matchup · Mean recorded OS 24.3Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Cokeado1 game · 11.1% of games in this matchup · Mean recorded OS 41.7Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Endersult1 game · 11.1% of games in this matchup · Mean recorded OS 25.2Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • gonpost1 game · 11.1% of games in this matchup · Mean recorded OS 32.2Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • smeet1 game · 11.1% of games in this matchup · Mean recorded OS 12.7Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • SturmRabe1 game · 11.1% of games in this matchup · Mean recorded OS 10.3Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • TurdBuns1 game · 11.1% of games in this matchup · Mean recorded OS 24.1Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Vinnievin1 game · 11.1% of games in this matchup · Mean recorded OS 23.5Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.

Front (second) vs Shared central front · shared frontline

3 matched games · 6 distinct opponents · Mean opponent OS 20.1.

Average economy and combat

Both sides use the same measured games for each row. Coverage is the share of games reaching that time with both measurements. Activity is against all enemies, not damage or spending against this lane opponent alone.

For shared Front, the opponent average is per opposing player in each game, and both opposing players must have records.

3 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponents (per player)Coverage
Metal producedTotal metal produced by this player by this time.3,708.3 metal4,761.5 metal100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,449.3 metal4,541.3 metal100.0%3 paired games
Energy producedTotal energy produced by this player by this time.40,012.9 energy50,788.5 energy100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.4,904.8 damage8,919.0 damage100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.4,617.8 damage7,000.8 damage100.0%3 paired games
Units producedTotal units produced by this time, including buildings.45.7 units46.2 units100.0%3 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.0%0 paired games
Metal lost to enemiesMetal cost of completed units and buildings lost to enemies by this time. Includes commanders; excludes unfinished units and reclaim. Wreckage recovered later is not subtracted.Not recordedNot recorded0.0%0 paired games
Enemy metal destroyedMetal cost of completed enemy units and buildings credited to this player for their destruction. Aircraft crashes can credit the last attacker. Includes commanders; excludes unfinished units. Assists are not counted.Not recordedNot recorded0.0%0 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.Not recordedNot recorded0.0%0 paired games
  • [Blahaj]varunda1 game · 33.3% of games in this matchup · Mean recorded OS 18.4Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • [Joe]Naboyk1 game · 33.3% of games in this matchup · Mean recorded OS 23.2Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • DDarkJoker1 game · 33.3% of games in this matchup · Mean recorded OS 21.4Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • pasdovqr1 game · 33.3% of games in this matchup · Mean recorded OS 11.8Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • pownage2271 game · 33.3% of games in this matchup · Mean recorded OS 32.5Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Schnitzel_von_Wagen1 game · 33.3% of games in this matchup · Mean recorded OS 13.2Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.

Two opposing frontline starts share this lane. Each opponent’s frequency uses the matched games, so the percentages can add up to more than 100%.

Front (suicide) vs Shared central front · shared frontline

3 matched games · 6 distinct opponents · Mean opponent OS 9.8.

Average economy and combat

Both sides use the same measured games for each row. Coverage is the share of games reaching that time with both measurements. Activity is against all enemies, not damage or spending against this lane opponent alone.

For shared Front, the opponent average is per opposing player in each game, and both opposing players must have records.

3 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponents (per player)Coverage
Metal producedTotal metal produced by this player by this time.4,056.6 metal3,770.0 metal100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,532.3 metal4,134.3 metal100.0%3 paired games
Energy producedTotal energy produced by this player by this time.36,937.9 energy43,684.9 energy100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.12,635.0 damage6,390.5 damage100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.6,869.6 damage10,685.5 damage100.0%3 paired games
Units producedTotal units produced by this time, including buildings.49.3 units41.3 units100.0%3 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.0%0 paired games
Metal lost to enemiesMetal cost of completed units and buildings lost to enemies by this time. Includes commanders; excludes unfinished units and reclaim. Wreckage recovered later is not subtracted.Not recordedNot recorded0.0%0 paired games
Enemy metal destroyedMetal cost of completed enemy units and buildings credited to this player for their destruction. Aircraft crashes can credit the last attacker. Includes commanders; excludes unfinished units. Assists are not counted.Not recordedNot recorded0.0%0 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.Not recordedNot recorded0.0%0 paired games
  • [SF]BattleDice1 game · 33.3% of games in this matchup · Mean recorded OS 9.8Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • [SF]Kramnog1 game · 33.3% of games in this matchup · Mean recorded OS 14.2Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • dgfr1 game · 33.3% of games in this matchup · Mean recorded OS 7.4Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Gremlinski1 game · 33.3% of games in this matchup · Mean recorded OS 13.8Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • lincomeyer20141 game · 33.3% of games in this matchup · Mean recorded OS 6.5Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • StrikerEureka1 game · 33.3% of games in this matchup · Mean recorded OS 6.9Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.

Two opposing frontline starts share this lane. Each opponent’s frequency uses the matched games, so the percentages can add up to more than 100%.

Geo sea vs Beach sea

4 matched games · 4 distinct opponents · Mean opponent OS 20.4.

Average economy and combat

Both sides use the same measured games for each row. Coverage is the share of games reaching that time with both measurements. Activity is against all enemies, not damage or spending against this lane opponent alone.

4 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponentCoverage
Metal producedTotal metal produced by this player by this time.3,191.5 metal4,310.2 metal100.0%4 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,840.2 metal4,400.8 metal100.0%4 paired games
Energy producedTotal energy produced by this player by this time.57,471.3 energy58,604.6 energy100.0%4 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.702.8 damage2,078.8 damage100.0%4 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.2,059.7 damage958.2 damage100.0%4 paired games
Units producedTotal units produced by this time, including buildings.36.8 units52.5 units100.0%4 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.0%0 paired games
Metal lost to enemiesMetal cost of completed units and buildings lost to enemies by this time. Includes commanders; excludes unfinished units and reclaim. Wreckage recovered later is not subtracted.Not recordedNot recorded0.0%0 paired games
Enemy metal destroyedMetal cost of completed enemy units and buildings credited to this player for their destruction. Aircraft crashes can credit the last attacker. Includes commanders; excludes unfinished units. Assists are not counted.Not recordedNot recorded0.0%0 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.Not recordedNot recorded0.0%0 paired games
  • HolyganaBanana1 game · 25.0% of games in this matchup · Mean recorded OS 26.1Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Lukeclari1 game · 25.0% of games in this matchup · Mean recorded OS 12.4Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Tetrakill1 game · 25.0% of games in this matchup · Mean recorded OS 23.1Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • TRancher1 game · 25.0% of games in this matchup · Mean recorded OS 20.2Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.

Why some selected games have no identified lane:

  • Starting layout not verified: 4 games.
  • No individual lane assigned for this position: 26 games.

Opponents are identified from verified starting lanes on Supreme Isthmus v2.1 in 8v8 games. Sea has one opposing player. The shared central front has two opposing starting players. Other positions have no fixed individual opponent assigned here. Team wins are whole-match results, not lane wins. Profile lane history includes all published Supreme Isthmus 8v8 games for this account.

Ask about this player

Open a prepared question for Supreme Isthmus v2.1, then adjust the map, position, game version or reference rating.

About these results

Included: 66 published games lasting at least five minutes, linked to account 597516. All recorded factions, game versions and formats are included in these activity totals. Opponents can include AI. Detailed analysis and rankings apply their own filters; their game counts can be smaller.

Available measurements: 100.0% of these games have usable unit-event data. Each trait or chart shows its own coverage. Missing measurements are unknown; a recorded zero means the measurement was made and nothing was recorded.

Still loading: a preparing label means an analysis has not finished. It does not mean the player has no history or never did that action.

Freshness: replay data published 14 Oct 2026, 09:22 UTC; this summary prepared 14 Oct 2026, 09:56 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.