BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 442441

arcsiz

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

Latest recorded OS
34.4
29 Sep 2026 · Large teams · 16 players
Recorded games
106
30 Aug 2026–29 Sep 2026 UTC
Maps played
7
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.

242026-09-05
to 2026-09-11
292026-09-12
to 2026-09-18
212026-09-19
to 2026-09-25
152026-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: 59.6% of selected games.

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

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

Beach sea vs Geo sea

6 matched games · 5 distinct opponents · Mean opponent OS 22.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.

6 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,449.1 metal3,466.9 metal100.0%6 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,002.5 metal3,826.0 metal100.0%6 paired games
Energy producedTotal energy produced by this player by this time.34,983.6 energy44,951.9 energy100.0%6 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,168.0 damage626.2 damage100.0%6 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.728.0 damage1,212.2 damage100.0%6 paired games
Units producedTotal units produced by this time, including buildings.35.0 units36.2 units100.0%6 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.0 units7.0 units33.3%2 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.108.2 metal232.6 metal83.3%5 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.201.8 metal108.2 metal83.3%5 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.6 units0.8 units83.3%5 paired games
  • mestertool2 games · 33.3% of games in this matchup · Mean recorded OS 8.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.
  • Askol_d1 game · 16.7% of games in this matchup · Mean recorded OS 22.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.
  • Dad_The_Speedrunner1 game · 16.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.
  • gmansawesome1 game · 16.7% of games in this matchup · Mean recorded OS 29.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.
  • soteiru1 game · 16.7% of games in this matchup · Mean recorded OS 27.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.

Front (second) vs Shared central front · shared frontline

8 matched games · 15 distinct opponents · Mean opponent OS 42.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.

8 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,463.5 metal4,112.2 metal100.0%8 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,136.0 metal4,398.0 metal100.0%8 paired games
Energy producedTotal energy produced by this player by this time.47,512.2 energy44,212.0 energy100.0%8 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.12,783.8 damage14,302.6 damage100.0%8 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.13,120.2 damage13,932.8 damage100.0%8 paired games
Units producedTotal units produced by this time, including buildings.41.1 units46.8 units100.0%8 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.7.0 units11.0 units12.5%1 paired game
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.1,741.0 metal1,183.2 metal75.0%6 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.782.5 metal2,191.0 metal75.0%6 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.8.0 units9.0 units75.0%6 paired games
  • _Hawkey_2 games · 25.0% of games in this matchup · Mean recorded OS 58.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.
  • [CC]CupOfCoffee1 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
  • [FCRD]Tragedy1 game · 12.5% of games in this matchup · Mean recorded OS 34.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.
  • Boozha1 game · 12.5% of games in this matchup · Mean recorded OS 31.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.
  • EpicTyrannus1 game · 12.5% of games in this matchup · Mean recorded OS 41.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.
  • Handicapping_mySelf1 game · 12.5% of games in this matchup · Mean recorded OS 35.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.
  • Hunfore1 game · 12.5% of games in this matchup · Mean recorded OS 31.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.
  • Immort1 game · 12.5% of games in this matchup · Mean recorded OS 56.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.
  • Leohvm1 game · 12.5% of games in this matchup · Mean recorded OS 48.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.
  • Naigel1 game · 12.5% of games in this matchup · Mean recorded OS 47.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.
  • Private_Gator1 game · 12.5% of games in this matchup · Mean recorded OS 30.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.
  • Satelite1 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
  • Soliloqueur1 game · 12.5% of games in this matchup · Mean recorded OS 41.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.
  • Viltrum1 game · 12.5% of games in this matchup · Mean recorded OS 41.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.
  • watermeloans1 game · 12.5% of games in this matchup · Mean recorded OS 59.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.

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

15 matched games · 28 distinct opponents · Mean opponent OS 26.6.

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.

15 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,185.4 metal3,784.1 metal100.0%15 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,475.1 metal4,198.4 metal100.0%15 paired games
Energy producedTotal energy produced by this player by this time.46,856.9 energy46,589.6 energy100.0%15 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.13,217.8 damage11,653.4 damage100.0%15 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.15,053.6 damage11,483.6 damage100.0%15 paired games
Units producedTotal units produced by this time, including buildings.46.7 units45.3 units100.0%15 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.15.3 units14.3 units20.0%3 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.1,799.7 metal1,302.7 metal93.3%14 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,650.5 metal1,453.9 metal93.3%14 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.6.6 units7.7 units93.3%14 paired games
  • Xzhinn3 games · 20.0% of games in this matchup · Mean recorded OS 51.3Profile 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.
  • [WNTR]_Fenris_SC21 game · 6.7% of games in this matchup · Mean recorded OS 24.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.
  • Alikn121 game · 6.7% of games in this matchup · Mean recorded OS 6.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.
  • bentheninja2244661 game · 6.7% of games in this matchup · Mean recorded OS 29.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.
  • CMCrisis1 game · 6.7% of games in this matchup · Mean recorded OS 14.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.
  • garyman711 game · 6.7% of games in this matchup · Mean recorded OS 12.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.
  • haaven1 game · 6.7% of games in this matchup · Mean recorded OS 47.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.
  • HALF_DALLAH_HABIT1 game · 6.7% of games in this matchup · Mean recorded OS 30.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.
  • Handicapping_mySelf1 game · 6.7% of games in this matchup · Mean recorded OS 35.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.
  • HeXiT221 game · 6.7% of games in this matchup · Mean recorded OS 16.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.
  • iiwii1 game · 6.7% of games in this matchup · Mean recorded OS 28.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.
  • ILIKE_2_ECO1 game · 6.7% of games in this matchup · Mean recorded OS 36.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.
  • IMOLDGREGG1 game · 6.7% of games in this matchup · Mean recorded OS 12.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.
  • JesusIsGod1 game · 6.7% of games in this matchup · Mean recorded OS 18.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.
  • Liutos1 game · 6.7% of games in this matchup · Mean recorded OS 22.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.
  • MischievousDragonGF1 game · 6.7% of games in this matchup · Mean recorded OS 37.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.
  • onion21 game · 6.7% of games in this matchup · Mean recorded OS 8.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.
  • PiedmontBell1 game · 6.7% 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.
  • Reasonable13371 game · 6.7% of games in this matchup · Mean recorded OS 32.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.
  • SauceDispenser1 game · 6.7% of games in this matchup · Mean recorded OS 33.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.

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 28 recorded opponents.

Geo sea vs Beach sea

27 matched games · 26 distinct opponents · Mean opponent OS 22.6.

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.

27 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,819.7 metal3,373.9 metal100.0%27 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,472.1 metal3,930.3 metal100.0%27 paired games
Energy producedTotal energy produced by this player by this time.48,534.4 energy36,309.9 energy100.0%27 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.646.0 damage1,591.4 damage100.0%27 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,570.4 damage773.0 damage100.0%27 paired games
Units producedTotal units produced by this time, including buildings.41.0 units33.2 units100.0%27 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.7 units2.3 units22.2%6 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.192.2 metal136.5 metal92.6%25 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.122.8 metal181.4 metal92.6%25 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.6 units0.6 units92.6%25 paired games
  • EpicTyrannus2 games · 7.4% of games in this matchup · Mean recorded OS 41.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.
  • 74902131 game · 3.7% of games in this matchup · Mean recorded OS 22.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.
  • Arthur_Chaos1 game · 3.7% of games in this matchup · Mean recorded OS 8.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.
  • BigJohnny21 game · 3.7% of games in this matchup · Mean recorded OS 28.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.
  • clayton761 game · 3.7% of games in this matchup · Mean recorded OS 9.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.
  • fanboi1 game · 3.7% of games in this matchup · Mean recorded OS 28.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.
  • FFFire1 game · 3.7% of games in this matchup · Mean recorded OS 9.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.
  • Hannodins1 game · 3.7% of games in this matchup · Mean recorded OS 37.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.
  • JYHAK1 game · 3.7% of games in this matchup · Mean recorded OS 14.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.
  • Kbot_my_Ahole1 game · 3.7% of games in this matchup · Mean recorded OS 35.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.
  • KoolAid1 game · 3.7% of games in this matchup · Mean recorded OS 11.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.
  • Kurultai1 game · 3.7% 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.
  • Maz51 game · 3.7% of games in this matchup · Mean recorded OS 7.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.
  • Michigan1 game · 3.7% of games in this matchup · Mean recorded OS 28.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.
  • MoritzGaming1 game · 3.7% of games in this matchup · Mean recorded OS 10.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.
  • NotLupus1 game · 3.7% of games in this matchup · Mean recorded OS 15.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.
  • Peaches_11 game · 3.7% of games in this matchup · Mean recorded OS 12.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.
  • PRO_XeliN1 game · 3.7% of games in this matchup · Mean recorded OS 11.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.
  • q[o_o]p1 game · 3.7% of games in this matchup · Mean recorded OS 34.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.
  • RAM_Exerior1 game · 3.7% of games in this matchup · Mean recorded OS 38.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.

Showing 20 of 26 recorded opponents.

Why some selected games have no identified lane:

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

Air

Supreme Isthmus v2.1 · Large teams · 16 players

51.1 / 100

14 scored games · 82.4% coverage.

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

Earlier vs recent: Higher in recent games. Recorded game scores 58.2 recent vs 42.9 earlier, split at 16 Sep 2026. Approximate change range: 4.8 to 24.5 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

45.5 / 100

10 scored games · 71.4% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 43.7 recent vs 42.3 earlier, split at 14 Sep 2026. Approximate change range: -18.4 to 21.9 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

47.2 / 100

16 scored games · 64.0% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 46.9 recent vs 45.5 earlier, split at 21 Sep 2026. Approximate change range: -12.9 to 15.3 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

47.4 / 100

7 scored games · 100.0% coverage.

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

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

Why this score?

Geo tech

Supreme Isthmus v2.1 · Large teams · 16 players

52.5 / 100

7 scored games · 87.5% 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, 10:46 UTC.

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

Geo sea

25 selected games

Opens with Bot Lab 72.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 72% 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

Air

18 selected games

Opens with Valiant 66.7%

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. Valiant was the first observed fighting unit start by 5:00 in 66.7% 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)

16 selected games

Economy-focused at 10:00 63.6%

At 10:00, economy’s share of completed build value is above both the matching group’s average and its 75th percentile (top-quarter cutoff). The fighting-unit share is below both its average and its 25th percentile (bottom-quarter cutoff). Both must happen in at least 60% of at least 10 games with data. This shows building priorities; it does not prove unsafe greed or poor play. This investment pattern appears in 63.6% of comparable measured games. Matching comparison games available for 78.6% of this player’s games with data. Each other player counts equally within a group with the same settings and game version. Results from those groups are combined to match this player’s mix of games.

Games with measurements for this trait: 68.8%.
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: 106 published games lasting at least five minutes, linked to account 442441. 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: 89.6% 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, 10:04 UTC; this summary prepared 02 Oct 2026, 10:14 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.