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
Measurement	Profile owner	Starting-lane opponent	Coverage
Metal producedTotal metal produced by this player by this time.	3,709.7 metal	3,905.5 metal	100.0%9 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,149.6 metal	4,419.0 metal	100.0%9 paired games
Energy producedTotal energy produced by this player by this time.	29,635.7 energy	52,128.7 energy	100.0%9 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	3,612.3 damage	1,395.7 damage	100.0%9 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	1,532.3 damage	3,454.6 damage	100.0%9 paired games
Units producedTotal units produced by this time, including buildings.	31.2 units	39.8 units	100.0%9 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	1.0 units	3.7 units	33.3%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.	120.1 metal	225.8 metal	88.9%8 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.	322.4 metal	101.9 metal	88.9%8 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	0.2 units	0.2 units	88.9%8 paired games

sirniho2 games · 22.2% of games in this matchup · Mean recorded OS 38.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.
BroodFather1 game · 11.1% of games in this matchup · Mean recorded OS 15.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.
dmbf221 game · 11.1% of games in this matchup · Mean recorded OS 11.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.
JesterB1 game · 11.1% of games in this matchup · Mean recorded OS 32.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.
KOT_1 game · 11.1% of games in this matchup · Mean recorded OS 39.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.
Neb13371 game · 11.1% 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.
PRO_Rerory1 game · 11.1% of games in this matchup · Mean recorded OS 51.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.
Thurley1 game · 11.1% 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.

Front (second) vs Shared central front · shared frontline

19 matched games · 31 distinct opponents · Mean opponent OS 33.8.

Average economy and combat

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

19 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,044.6 metal	3,957.3 metal	100.0%19 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,553.4 metal	4,429.3 metal	100.0%19 paired games
Energy producedTotal energy produced by this player by this time.	51,049.0 energy	46,851.2 energy	100.0%19 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	11,423.2 damage	12,651.8 damage	100.0%19 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	12,098.1 damage	12,701.6 damage	100.0%19 paired games
Units producedTotal units produced by this time, including buildings.	49.0 units	46.5 units	100.0%19 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	6.6 units	14.1 units	52.6%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.	801.0 metal	1,498.8 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.	1,110.8 metal	1,167.3 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.	4.4 units	7.3 units	89.5%17 paired games

Chxad3 games · 15.8% of games in this matchup · Mean recorded OS 48.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.
_X_2 games · 10.5% of games in this matchup · Mean recorded OS 47.9Profile 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.
Gieds2 games · 10.5% 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.
HALF_DALLAH_HABIT2 games · 10.5% of games in this matchup · Mean recorded OS 31.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.
PlatinumBlonde2 games · 10.5% of games in this matchup · Mean recorded OS 56.4Profile 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.
PongoPygmaeus2 games · 10.5% of games in this matchup · Mean recorded OS 32.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.
0neTw01 game · 5.3% of games in this matchup · Mean recorded OS 39.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.
[Crd]Claps1 game · 5.3% of games in this matchup · Mean recorded OS 30.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.
[Crd]JayDX1 game · 5.3% of games in this matchup · Mean recorded OS 6.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.
azerty8891 game · 5.3% of games in this matchup · Mean recorded OS 4.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.
BigUglyBear1 game · 5.3% of games in this matchup · Mean recorded OS 27.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.
Boozha1 game · 5.3% 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.
braindump1 game · 5.3% of games in this matchup · Mean recorded OS 21.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.
ChaosNX1 game · 5.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.
Godmother131 game · 5.3% of games in this matchup · Mean recorded OS 37.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.
Hummell1 game · 5.3% of games in this matchup · Mean recorded OS 45.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.
ITz_LUZx1 game · 5.3% of games in this matchup · Mean recorded OS 22.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.
JesterB1 game · 5.3% of games in this matchup · Mean recorded OS 33.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.
Labr1 game · 5.3% of games in this matchup · Mean recorded OS 21.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.
MDam1 game · 5.3% of games in this matchup · Mean recorded OS 24.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 31 recorded opponents.

Front (suicide) vs Shared central front · shared frontline

68 matched games · 96 distinct opponents · Mean opponent OS 31.5.

Average economy and combat

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

68 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,353.7 metal	3,713.2 metal	100.0%68 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,793.6 metal	4,307.0 metal	100.0%68 paired games
Energy producedTotal energy produced by this player by this time.	51,067.1 energy	45,767.8 energy	100.0%68 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	14,586.5 damage	11,760.1 damage	100.0%68 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	13,952.5 damage	12,124.7 damage	100.0%68 paired games
Units producedTotal units produced by this time, including buildings.	50.9 units	44.3 units	100.0%68 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	11.4 units	12.4 units	26.5%18 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,237.2 metal	1,327.6 metal	86.8%59 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,552.6 metal	1,156.0 metal	86.8%59 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.0 units	86.8%59 paired games

Xad7 games · 10.3% of games in this matchup · Mean recorded OS 47.6Profile owner’s team won 71.4% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
_X_5 games · 7.3% of games in this matchup · Mean recorded OS 48.5Profile owner’s team won 40.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
PRO_Rerory4 games · 5.9% of games in this matchup · Mean recorded OS 49.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.
[Crd]ALRO3 games · 4.4% of games in this matchup · Mean recorded OS 15.2Profile owner’s team won 66.7% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
[Crd]Atlas3 games · 4.4% of games in this matchup · Mean recorded OS 28.9Profile owner’s team won 66.7% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
CentientWaffle3 games · 4.4% of games in this matchup · Mean recorded OS 32.9Profile owner’s team won 66.7% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
Immort3 games · 4.4% of games in this matchup · Mean recorded OS 53.5Profile 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.
Soliloqueur3 games · 4.4% of games in this matchup · Mean recorded OS 40.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.
zeus_on_god3 games · 4.4% of games in this matchup · Mean recorded OS 38.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.
[Crd]DeAnthony2 games · 2.9% of games in this matchup · Mean recorded OS 20.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.
[Crd]TTAC2 games · 2.9% of games in this matchup · Mean recorded OS 13.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.
[WNTR]_Fenris_SC22 games · 2.9% of games in this matchup · Mean recorded OS 25.6Profile 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.
Adeus2 games · 2.9% of games in this matchup · Mean recorded OS 36.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.
Bishtou2 games · 2.9% of games in this matchup · Mean recorded OS 27.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.
DouglasBacon2 games · 2.9% of games in this matchup · Mean recorded OS 30.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.
Eagles43002 games · 2.9% of games in this matchup · Mean recorded OS 17.7Profile 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.
Etherift2 games · 2.9% of games in this matchup · Mean recorded OS 33.4Profile 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.
HALF_DALLAH_HABIT2 games · 2.9% of games in this matchup · Mean recorded OS 30.7Profile 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.
heihallo2 games · 2.9% of games in this matchup · Mean recorded OS 28.9Profile 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.
Leohvm2 games · 2.9% of games in this matchup · Mean recorded OS 49.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.

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

Geo sea vs Beach sea

3 matched games · 3 distinct opponents · Mean opponent OS 26.2.

Average economy and combat

3 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,171.5 metal	3,520.5 metal	100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,929.8 metal	4,109.2 metal	100.0%3 paired games
Energy producedTotal energy produced by this player by this time.	53,529.0 energy	45,253.5 energy	100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	803.2 damage	1,585.6 damage	100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	1,196.0 damage	2,314.0 damage	100.0%3 paired games
Units producedTotal units produced by this time, including buildings.	44.3 units	40.7 units	100.0%3 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	3.7 units	8.3 units	100.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.	158.7 metal	277.0 metal	100.0%3 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.	140.0 metal	253.0 metal	100.0%3 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	0.0 units	0.3 units	100.0%3 paired games

adoadoado1 game · 33.3% 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.
cylant1 game · 33.3% 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.
Kbot_my_Ahole1 game · 33.3% of games in this matchup · Mean recorded OS 36.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.

Why some selected games have no identified lane:

Starting layout not verified: 1 game.
No individual lane assigned for this position: 22 games.
Starting-position records unavailable: 3 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.

Front (second)

Supreme Isthmus v2.1 · Large teams · 16 players

56.4 / 100

15 scored games · 75.0% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 61.7 recent vs 57.9 earlier, split at 14 Sep 2026. Approximate change range: -13.7 to 18.8 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.2 / 100

45 scored games · 73.8% coverage.

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

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

Why this score?

Geo tech

Supreme Isthmus v2.1 · Large teams · 16 players

53.0 / 100

13 scored games · 72.2% coverage.

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

Earlier vs recent: Higher in recent games. Recorded game scores 66.3 recent vs 44.5 earlier, split at 20 Sep 2026. Approximate change range: 6.9 to 30.8 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

54.0 / 100

6 scored games · 66.7% 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:45 UTC.

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

Geo sea

3 selected games

More measured games are needed for traits.

Explore this position

Tech

2 selected games

More measured games are needed for traits.

Explore this position

Front (suicide)

66 selected games

Economy-focused at 10:00 75.0%

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 75% of comparable measured games. Matching comparison games available for 72.7% 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: 60.6%.

Opens with Centurion 84.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. Centurion was the first observed fighting unit start by 5:00 in 84.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

Front (second)

19 selected games

Rocketeer-heavy by 10:00 66.7%

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

Games with measurements for this trait: 78.9%.

Opens with Pawn 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. Pawn 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

Geo tech

17 selected games

Opens with Bot Lab 94.1%

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

9 selected games

More measured games are needed for traits.

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