BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 573442

waine

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

Latest recorded OS: 32.0

Recorded games: 105

Maps played: 11

Recent activity

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

152026-09-05
to 2026-09-11

232026-09-12
to 2026-09-18

302026-09-19
to 2026-09-25

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

Supreme Isthmus v2.1

86.7% of recorded games · 91 games

Front (suicide)17.6%

Tech17.6%

Air15.4%

Unit-event data available: 90.1%.

Analyse / compare Explore Statistics

Altair_Crossing_V4.1

1.9% of recorded games · 2 games

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

Comet Catcher Remake 1.8

1.9% of recorded games · 2 games

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

Eternal Consequences 1.2

1.9% of recorded games · 2 games

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

Pyroclast 1.0.3

1.9% of recorded games · 2 games

Sea · P15100.0%

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

Canis River v1.4

1.0% of recorded games · 1 games

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

Center Command BAR v1.0

1.0% of recorded games · 1 games

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

Eye Of Horus 1.7.1

1.0% of recorded games · 1 games

Unit-event data available: 100.0%.

Analyse / compare Explore Statistics

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

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

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

Beach sea vs Geo sea

19 matched games · 14 distinct opponents · Mean opponent OS 28.3.

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.

19 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
Measurement	Profile owner	Starting-lane opponent	Coverage
Metal producedTotal metal produced by this player by this time.	3,775.1 metal	3,636.9 metal	100.0%19 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,136.7 metal	4,338.4 metal	100.0%19 paired games
Energy producedTotal energy produced by this player by this time.	36,886.2 energy	42,767.6 energy	100.0%19 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	1,664.1 damage	1,137.6 damage	100.0%19 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	1,332.3 damage	1,552.2 damage	100.0%19 paired games
Units producedTotal units produced by this time, including buildings.	33.9 units	40.7 units	100.0%19 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	3.6 units	4.3 units	47.4%9 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.	211.3 metal	224.0 metal	89.5%17 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.	269.6 metal	203.0 metal	89.5%17 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	1.8 units	0.7 units	89.5%17 paired games

SHOGVN5 games · 26.3% of games in this matchup · Mean recorded OS 36.5Profile owner’s team won 60.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
JesterB2 games · 10.5% of games in this matchup · Mean recorded OS 32.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.
[AOC]BigTomato071 game · 5.3% of games in this matchup · Mean recorded OS 12.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.
[MooDeng]NongJohn1 game · 5.3% of games in this matchup · Mean recorded OS 39.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.
Alphacure1 game · 5.3% of games in this matchup · Mean recorded OS 36.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.
BraucheAuchRucola1 game · 5.3% of games in this matchup · Mean recorded OS 18.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.
chrisillingworth1 game · 5.3% of games in this matchup · Mean recorded OS 5.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.
cmilly1 game · 5.3% of games in this matchup · Mean recorded OS 16.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.
d4rklight1 game · 5.3% of games in this matchup · Mean recorded OS 25.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.
darkstar231 game · 5.3% of games in this matchup · Mean recorded OS 36.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.
El_Turco1 game · 5.3% of games in this matchup · Mean recorded OS 32.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.
Nomenclature1 game · 5.3% of games in this matchup · Mean recorded OS 15.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.
Rexalidus1 game · 5.3% of games in this matchup · Mean recorded OS 37.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.
titan2gamer1 game · 5.3% of games in this matchup · Mean recorded OS 14.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

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

2 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
Measurement	Profile owner	Starting-lane opponents (per player)	Coverage
Metal producedTotal metal produced by this player by this time.	4,166.5 metal	3,463.2 metal	100.0%2 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	5,025.0 metal	4,348.7 metal	100.0%2 paired games
Energy producedTotal energy produced by this player by this time.	51,377.4 energy	49,076.4 energy	100.0%2 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	8,032.1 damage	8,259.1 damage	100.0%2 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	7,362.9 damage	9,578.5 damage	100.0%2 paired games
Units producedTotal units produced by this time, including buildings.	50.0 units	45.2 units	100.0%2 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	Not recorded	Not recorded	0.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.	586.0 metal	912.5 metal	100.0%2 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.	553.0 metal	525.5 metal	100.0%2 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	6.0 units	6.2 units	100.0%2 paired games

omga1 game · 50.0% of games in this matchup · Mean recorded OS 26.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.
ReduceReclaimRez1 game · 50.0% 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.
TrifectaShadow1 game · 50.0% of games in this matchup · Mean recorded OS 10.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.
x3no1 game · 50.0% of games in this matchup · Mean recorded OS 26.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.

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

16 matched games · 31 distinct opponents · Mean opponent OS 23.5.

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.

16 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
Measurement	Profile owner	Starting-lane opponents (per player)	Coverage
Metal producedTotal metal produced by this player by this time.	4,112.8 metal	3,985.5 metal	100.0%16 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,580.5 metal	4,289.1 metal	100.0%16 paired games
Energy producedTotal energy produced by this player by this time.	45,923.7 energy	45,527.4 energy	100.0%16 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	10,958.2 damage	8,296.2 damage	100.0%16 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	9,763.0 damage	9,443.8 damage	100.0%16 paired games
Units producedTotal units produced by this time, including buildings.	45.8 units	44.6 units	100.0%16 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	14.7 units	14.2 units	18.8%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,063.1 metal	1,182.2 metal	100.0%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,492.1 metal	1,107.5 metal	100.0%16 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	3.6 units	7.4 units	100.0%16 paired games

[crd]sisa2 games · 12.5% of games in this matchup · Mean recorded OS 43.3Profile 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.
[Crd]Glizzy1 game · 6.2% of games in this matchup · Mean recorded OS 21.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.
[Crd]Stinky0161 game · 6.2% of games in this matchup · Mean recorded OS 13.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.
[FSK21]Modius1 game · 6.2% 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.
[Grump]Atlasfailed1 game · 6.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.
[I]_[I]1 game · 6.2% of games in this matchup · Mean recorded OS 10.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.
_Astartes_1 game · 6.2% of games in this matchup · Mean recorded OS 14.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.
a11fred1 game · 6.2% of games in this matchup · Mean recorded OS 26.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.
AbyssFalcon1 game · 6.2% of games in this matchup · Mean recorded OS 30.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.
Bishtou1 game · 6.2% of games in this matchup · Mean recorded OS 28.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.
bndrylyr1 game · 6.2% of games in this matchup · Mean recorded OS 12.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.
Canned_Possum1 game · 6.2% of games in this matchup · Mean recorded OS 25.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.
Chancho1 game · 6.2% of games in this matchup · Mean recorded OS 32.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.
death4uandme1 game · 6.2% of games in this matchup · Mean recorded OS 26.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.
EnclaveGeneralSlick1 game · 6.2% of games in this matchup · Mean recorded OS 10.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.
Giverrion1 game · 6.2% of games in this matchup · Mean recorded OS 12.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.
Horobchyk1 game · 6.2% of games in this matchup · Mean recorded OS 23.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.
horseAus1 game · 6.2% of games in this matchup · Mean recorded OS 18.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.
Hunfore1 game · 6.2% of games in this matchup · Mean recorded OS 31.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.
MurderBotCog1 game · 6.2% of games in this matchup · Mean recorded OS 18.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.

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

Geo sea vs Beach sea

12 matched games · 12 distinct opponents · Mean opponent OS 22.9.

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.

12 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
Measurement	Profile owner	Starting-lane opponent	Coverage
Metal producedTotal metal produced by this player by this time.	4,150.0 metal	3,574.1 metal	100.0%12 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	5,075.4 metal	4,095.6 metal	100.0%12 paired games
Energy producedTotal energy produced by this player by this time.	45,835.4 energy	38,662.2 energy	100.0%12 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	1,243.6 damage	1,181.8 damage	100.0%12 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	1,171.4 damage	1,315.6 damage	100.0%12 paired games
Units producedTotal units produced by this time, including buildings.	39.9 units	37.8 units	100.0%12 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	2.2 units	3.8 units	66.7%8 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.	107.0 metal	217.7 metal	75.0%9 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.	213.0 metal	117.4 metal	75.0%9 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	0.3 units	0.7 units	75.0%9 paired games

akov1 game · 8.3% of games in this matchup · Mean recorded OS 18.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.
Doydle1 game · 8.3% of games in this matchup · Mean recorded OS 22.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.
Ender_the_Warrior1 game · 8.3% of games in this matchup · Mean recorded OS 26.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.
fanboi1 game · 8.3% of games in this matchup · Mean recorded OS 32.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.
HorseWalksIntoABAR1 game · 8.3% of games in this matchup · Mean recorded OS 13.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 · 8.3% 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.
ikilldatitanic1 game · 8.3% of games in this matchup · Mean recorded OS 12.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.
JesterB1 game · 8.3% of games in this matchup · Mean recorded OS 32.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 · 8.3% of games in this matchup · Mean recorded OS 16.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.
Lacky1 game · 8.3% of games in this matchup · Mean recorded OS 11.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.
Late111 game · 8.3% of games in this matchup · Mean recorded OS 22.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.
soxfannh1 game · 8.3% of games in this matchup · Mean recorded OS 18.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.

Why some selected games have no identified lane:

No individual lane assigned for this position: 41 games.
Starting-position records unavailable: 1 game.

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

54.5 / 100

11 scored games · 78.6% coverage.

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

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

Why this score?

Beach sea

Supreme Isthmus v2.1 · Large teams · 16 players

55.5 / 100

16 scored games · 88.9% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 54.9 recent vs 63.1 earlier, split at 16 Sep 2026. Approximate change range: -26.7 to 14.1 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

53.7 / 100

14 scored games · 100.0% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 58.9 recent vs 54.3 earlier, split at 19 Sep 2026. Approximate change range: -0.5 to 18.3 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

50.5 / 100

15 scored games · 93.8% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 53.8 recent vs 46.3 earlier, split at 14 Sep 2026. Approximate change range: -6.1 to 20.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

61.0 / 100

7 scored games · 77.8% 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

55.4 / 100

8 scored games · 80.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-03–2026-10-02 UTC · Supreme Isthmus v2.1 · human 8v8 · mirrored starts combined. Checked 02 Oct 2026, 10:50 UTC.

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

Geo sea

13 selected games

Opens with Bot Lab 76.9%

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

Tech

15 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

Air

13 selected games

Opens with Valiant 84.6%

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 84.6% 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)

14 selected games

Rocketeer-heavy by 10:00 78.6%

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 78.6% of comparable measured games. Average built in games with data: 25.36 Rocketeer units by 10:00.

Games with measurements for this trait: 100.0%.

Opens with Tick 100.0%

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. Tick was the first observed fighting unit 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 (second)

2 selected games

More measured games are needed for traits.

Explore this position

Geo tech

8 selected games

More measured games are needed for traits.

Explore this position

Beach sea

17 selected games

No repeated habit met the trait rules in this position.

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 unit First T2 constructor Units received from teammates Builds after enemy bombers

About these results

Included: 105 published games lasting at least five minutes, linked to account 573442. 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: 91.4% 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.