BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 473801

Damsko

A quick view of this player’s published replay history. Choose a map below to explore their play in more detail.

Latest recorded OS
38.5
29 Sep 2026 · Large teams · 16 players
Recorded games
164
30 Aug 2026–29 Sep 2026 UTC
Maps played
4
Map versions counted separately

Recent activity

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

432026-09-05
to 2026-09-11
332026-09-12
to 2026-09-18
322026-09-19
to 2026-09-25
192026-09-26
to 2026-10-02

Most played maps & positions

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

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: 58.8% of selected games.

Selected games: 160 · Games with identified lanes: 94.

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

Beach sea vs Geo sea

43 matched games · 33 distinct opponents · Mean opponent OS 33.2.

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.

43 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,486.5 metal3,946.5 metal100.0%43 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,356.9 metal4,635.3 metal100.0%43 paired games
Energy producedTotal energy produced by this player by this time.39,208.9 energy48,749.3 energy100.0%43 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,206.2 damage595.6 damage100.0%43 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.744.2 damage1,116.8 damage100.0%43 paired games
Units producedTotal units produced by this time, including buildings.34.6 units39.1 units100.0%43 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.3 units2.4 units23.3%10 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.112.0 metal157.8 metal90.7%39 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.193.6 metal83.6 metal90.7%39 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.3 units0.6 units90.7%39 paired games
  • Hummell3 games · 7.0% of games in this matchup · Mean recorded OS 47.0Profile owner’s team won 33.3% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • JesterB3 games · 7.0% of games in this matchup · Mean recorded OS 34.7Profile owner’s team won 33.3% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • CentientWaffle2 games · 4.7% of games in this matchup · Mean recorded OS 32.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.
  • Chancho2 games · 4.7% of games in this matchup · Mean recorded OS 27.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.
  • hihimik2 games · 4.7% of games in this matchup · Mean recorded OS 35.7Profile 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.
  • pyrothraxus2 games · 4.7% of games in this matchup · Mean recorded OS 37.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.
  • SHOGVN2 games · 4.7% of games in this matchup · Mean recorded OS 36.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.
  • sirniho2 games · 4.7% of games in this matchup · Mean recorded OS 37.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.
  • 0neTw01 game · 2.3% of games in this matchup · Mean recorded OS 40.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.
  • 3xcentric1 game · 2.3% of games in this matchup · Mean recorded OS 20.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.
  • Adeus1 game · 2.3% of games in this matchup · Mean recorded OS 36.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.
  • AllINoRNOTHING1 game · 2.3% of games in this matchup · Mean recorded OS 18.7Profile 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.
  • blazeitken1 game · 2.3% of games in this matchup · Mean recorded OS 30.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.
  • Bone_White1 game · 2.3% of games in this matchup · Mean recorded OS 21.6Profile 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.
  • Copperfield1 game · 2.3% of games in this matchup · Mean recorded OS 14.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.
  • Dad_The_Speedrunner1 game · 2.3% of games in this matchup · Mean recorded OS 34.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.
  • DukeofStars1 game · 2.3% of games in this matchup · Mean recorded OS 55.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.
  • El_Turco1 game · 2.3% of games in this matchup · Mean recorded OS 29.9Profile 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.
  • Elpapuedu0011 game · 2.3% of games in this matchup · Mean recorded OS 14.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.
  • enderOS11 game · 2.3% of games in this matchup · Mean recorded OS 34.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.

Showing 20 of 33 recorded opponents.

Front (second) vs Shared central front · shared frontline

24 matched games · 40 distinct opponents · Mean opponent OS 36.0.

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.

24 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,872.7 metal3,601.8 metal100.0%24 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,499.3 metal4,171.0 metal100.0%24 paired games
Energy producedTotal energy produced by this player by this time.47,884.7 energy45,951.1 energy100.0%24 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.10,812.8 damage11,880.1 damage100.0%24 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.9,645.9 damage11,557.8 damage100.0%24 paired games
Units producedTotal units produced by this time, including buildings.42.0 units46.6 units100.0%24 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.11.2 units13.2 units41.7%10 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.977.0 metal1,276.1 metal83.3%20 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.1,236.8 metal1,350.4 metal83.3%20 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.6.5 units7.3 units83.3%20 paired games
  • Xzhinn6 games · 25.0% of games in this matchup · Mean recorded OS 49.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.
  • GazzGrim2 games · 8.3% of games in this matchup · Mean recorded OS 30.8Profile owner’s team won 50.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • haaven2 games · 8.3% of games in this matchup · Mean recorded OS 47.0Profile 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.
  • watermeloans2 games · 8.3% of games in this matchup · Mean recorded OS 60.0Profile owner’s team won 50.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • [BS]RohNiN1 game · 4.2% of games in this matchup · Mean recorded OS 39.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.
  • [crd]sisa1 game · 4.2% of games in this matchup · Mean recorded OS 43.7Profile 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.
  • [DmE]thespaceMIR1 game · 4.2% of games in this matchup · Mean recorded OS 14.6Profile 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.
  • [GHT]Gammablast5671 game · 4.2% of games in this matchup · Mean recorded OS 23.3Profile 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.
  • [Grump]Boomer911 game · 4.2% of games in this matchup · Mean recorded OS 14.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.
  • Adeus1 game · 4.2% of games in this matchup · Mean recorded OS 36.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.
  • Azzap1 game · 4.2% of games in this matchup · Mean recorded OS 16.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.
  • Boozha1 game · 4.2% of games in this matchup · Mean recorded OS 33.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.
  • CentientWaffle1 game · 4.2% of games in this matchup · Mean recorded OS 34.6Profile 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.
  • death4uandme1 game · 4.2% of games in this matchup · Mean recorded OS 25.9Profile 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.
  • derkarl1 game · 4.2% of games in this matchup · Mean recorded OS 38.6Profile 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.
  • DRM1 game · 4.2% of games in this matchup · Mean recorded OS 43.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.
  • Farindoor1 game · 4.2% of games in this matchup · Mean recorded OS 25.0Profile 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.
  • Gieds1 game · 4.2% of games in this matchup · Mean recorded OS 47.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.
  • heart_attack1 game · 4.2% of games in this matchup · Mean recorded OS 35.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.
  • hoze1 game · 4.2% of games in this matchup · Mean recorded OS 26.9Profile 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%.

Showing 20 of 40 recorded opponents.

Front (suicide) vs Shared central front · shared frontline

17 matched games · 32 distinct opponents · Mean opponent OS 27.7.

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.

17 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,225.9 metal3,705.9 metal100.0%17 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,864.1 metal4,117.6 metal100.0%17 paired games
Energy producedTotal energy produced by this player by this time.48,273.4 energy47,145.3 energy100.0%17 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.13,720.0 damage9,227.0 damage100.0%17 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.11,016.5 damage11,285.5 damage100.0%17 paired games
Units producedTotal units produced by this time, including buildings.48.8 units43.2 units100.0%17 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.7.0 units9.2 units23.5%4 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.868.9 metal1,173.9 metal94.1%16 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.1,120.7 metal843.9 metal94.1%16 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.3.8 units6.3 units94.1%16 paired games
  • Fanatico2 games · 11.8% of games in this matchup · Mean recorded OS 16.6Profile 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.
  • PRO_Rerory2 games · 11.8% of games in this matchup · Mean recorded OS 49.3Profile 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.
  • _[BOBO]_1 game · 5.9% 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.
  • annie_may_tydease1 game · 5.9% of games in this matchup · Mean recorded OS 31.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.
  • AxonYorvast1 game · 5.9% 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.
  • blazeitken1 game · 5.9% of games in this matchup · Mean recorded OS 30.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.
  • Chancho1 game · 5.9% of games in this matchup · Mean recorded OS 24.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.
  • CommanderBoxEater1 game · 5.9% of games in this matchup · Mean recorded OS 29.6Profile 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.
  • CompostSlingeR1 game · 5.9% of games in this matchup · Mean recorded OS 34.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.
  • DellusionalPig1 game · 5.9% of games in this matchup · Mean recorded OS 10.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.
  • Detriment1 game · 5.9% of games in this matchup · Mean recorded OS 20.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.
  • Diron591 game · 5.9% of games in this matchup · Mean recorded OS 14.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.
  • DontPanic521 game · 5.9% of games in this matchup · Mean recorded OS 12.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.
  • Elpapuedu0011 game · 5.9% of games in this matchup · Mean recorded OS 15.0Profile 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.
  • fbots19981 game · 5.9% of games in this matchup · Mean recorded OS 21.3Profile 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.
  • FIynn1 game · 5.9% of games in this matchup · Mean recorded OS 15.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.
  • Hummell1 game · 5.9% of games in this matchup · Mean recorded OS 45.6Profile 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.
  • HuntressesofArtemis1 game · 5.9% of games in this matchup · Mean recorded OS 36.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.
  • Immort1 game · 5.9% of games in this matchup · Mean recorded OS 52.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.
  • ISX1 game · 5.9% of games in this matchup · Mean recorded OS 17.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.

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%.

Showing 20 of 32 recorded opponents.

Geo sea vs Beach sea

10 matched games · 10 distinct opponents · Mean opponent OS 27.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.

10 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.4,159.9 metal3,369.3 metal100.0%10 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,989.1 metal4,103.3 metal100.0%10 paired games
Energy producedTotal energy produced by this player by this time.44,369.7 energy35,982.7 energy100.0%10 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,273.0 damage976.1 damage100.0%10 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.901.8 damage1,412.5 damage100.0%10 paired games
Units producedTotal units produced by this time, including buildings.40.4 units35.4 units100.0%10 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.98.4 metal280.4 metal100.0%10 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.258.1 metal144.2 metal100.0%10 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.4 units0.7 units100.0%10 paired games
  • Adeus1 game · 10.0% of games in this matchup · Mean recorded OS 37.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.
  • El_Turco1 game · 10.0% of games in this matchup · Mean recorded OS 30.0Profile 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.
  • fenekooo1 game · 10.0% of games in this matchup · Mean recorded OS 17.9Profile 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.
  • GeeGee1 game · 10.0% of games in this matchup · Mean recorded OS 35.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.
  • haaven1 game · 10.0% of games in this matchup · Mean recorded OS 46.6Profile 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.
  • KillerKernel1 game · 10.0% of games in this matchup · Mean recorded OS 26.0Profile 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.
  • RedLine7371 game · 10.0% of games in this matchup · Mean recorded OS 18.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.
  • Triac1 game · 10.0% of games in this matchup · Mean recorded OS 18.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.
  • Vaticineur1 game · 10.0% of games in this matchup · Mean recorded OS 32.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.
  • ZsyrusZ1 game · 10.0% of games in this matchup · Mean recorded OS 7.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.

Why some selected games have no identified lane:

  • No individual lane assigned for this position: 61 games.
  • Starting-position records unavailable: 5 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.

Performance by position

Prepared ranking results, with the same calculation and evidence as the rankings page. Scores are not OS or a share of team victory.

Geo tech

Supreme Isthmus v2.1 · Large teams · 16 players

62.0 / 100

24 scored games · 72.7% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 66.7 recent vs 64.7 earlier, split at 16 Sep 2026. Approximate change range: -6.0 to 10.2 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Beach sea

Supreme Isthmus v2.1 · Large teams · 16 players

61.5 / 100

36 scored games · 87.8% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 65.1 recent vs 65.1 earlier, split at 10 Sep 2026. Approximate change range: -9.9 to 9.7 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Front (second)

Supreme Isthmus v2.1 · Large teams · 16 players

57.8 / 100

20 scored games · 87.0% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 60.6 recent vs 65.1 earlier, split at 10 Sep 2026. Approximate change range: -17.1 to 4.4 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Front (suicide)

Supreme Isthmus v2.1 · Large teams · 16 players

54.9 / 100

14 scored games · 93.3% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 52.4 recent vs 62.4 earlier, split at 11 Sep 2026. Approximate change range: -23.7 to 5.7 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Tech

Supreme Isthmus v2.1 · Large teams · 16 players

52.2 / 100

11 scored games · 91.7% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 55.6 recent vs 50.8 earlier, split at 13 Sep 2026. Approximate change range: -5.7 to 18.0 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Geo sea

Supreme Isthmus v2.1 · Large teams · 16 players

60.0 / 100

9 scored games · 90.0% coverage.

Early results · Updated 02 Oct 2026, 08:39 UTC

Recent comparison: more measured games are needed in both periods.

Why this score?

Playstyle at a glance

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.

Trait period: 2026-09-02–2026-10-01 UTC · Supreme Isthmus v2.1 · human 8v8 · mirrored starts combined. Checked 02 Oct 2026, 09:47 UTC.

These traits are awaiting a refresh. They describe the period printed above.

Tech

12 selected games

Opens with Bot Lab 100.0%

The same first observed factory start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Bot Lab was the first observed factory start by 5:00 in 100% of measured openings. Openings without this build and tied starts of different unit types stay in the percentage. A start need not finish.

Games with measurements for this trait: 100.0%.
Explore this position

Front (suicide)

12 selected games

Rocketeer-heavy by 10:00 60.0%

By 10:00, completed at least 5 Rocketeer units representing at least 50% of all completed mobile combat-unit metal value. The unit count must also be above both the matching group’s average and its 75th percentile (the cutoff for the top quarter), in at least 60% of at least 10 matching games with data. Only eligible observed starts and completions count. This is a production preference, not evidence of a rush or attack. This focused opening appears in 60% of comparable measured games. Average built in games with data: 24.58 Rocketeer units by 10:00.

Games with measurements for this trait: 83.3%.
Opens with Bot Lab 75.0%

The same first observed factory start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Bot Lab was the first observed factory start by 5:00 in 75% of measured openings. Openings without this build and tied starts of different unit types stay in the percentage. A start need not finish.

Games with measurements for this trait: 100.0%.
Explore this position

Front (second)

26 selected games

Blitz-heavy by 10:00 85.0%

By 10:00, completed at least 5 Blitz units representing at least 50% of all completed mobile combat-unit metal value. The unit count must also be above both the matching group’s average and its 75th percentile (the cutoff for the top quarter), in at least 60% of at least 10 matching games with data. Only eligible observed starts and completions count. This is a production preference, not evidence of a rush or attack. This focused opening appears in 85% of comparable measured games. Average built in games with data: 24.84 Blitz units by 10:00.

Games with measurements for this trait: 76.9%.
Opens with Rover 80.8%

The same first observed fighting unit start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Rover was the first observed fighting unit start by 5:00 in 80.8% of measured openings. Openings without this build and tied starts of different unit types stay in the percentage. A start need not finish.

Games with measurements for this trait: 100.0%.
Explore this position

Geo tech

33 selected games

Opens with Bot Lab 100.0%

The same first observed factory start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Bot Lab was the first observed factory start by 5:00 in 100% of measured openings. Openings without this build and tied starts of different unit types stay in the percentage. A start need not finish.

Games with measurements for this trait: 100.0%.
Explore this position

Beach sea

42 selected games

Opens with Shipyard 100.0%

The same first observed factory start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Shipyard was the first observed factory start by 5:00 in 100% of measured openings. Openings without this build and tied starts of different unit types stay in the percentage. A start need not finish.

Games with measurements for this trait: 100.0%.
Explore this position

Ask about this player

Open a prepared question for the most played map, then adjust the map, position, game version or reference rating.

Common first fighting unitFirst T2 constructorUnits received from teammatesBuilds after enemy bombers
About these results

Included: 164 published games lasting at least five minutes, linked to account 473801. 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: 92.1% 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 02 Oct 2026, 09:26 UTC; this summary prepared 02 Oct 2026, 09:48 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.