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
Measurement	Profile owner	Starting-lane opponents (per player)	Coverage
Metal producedTotal metal produced by this player by this time.	4,033.2 metal	3,527.7 metal	100.0%15 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,696.9 metal	4,225.0 metal	100.0%15 paired games
Energy producedTotal energy produced by this player by this time.	46,314.3 energy	48,335.7 energy	100.0%15 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	13,736.1 damage	11,120.8 damage	100.0%15 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	8,671.0 damage	13,847.0 damage	100.0%15 paired games
Units producedTotal units produced by this time, including buildings.	50.1 units	46.4 units	100.0%15 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	13.4 units	15.6 units	33.3%5 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,192.1 metal	1,313.0 metal	93.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,530.1 metal	1,087.8 metal	93.3%14 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	7.5 units	7.6 units	93.3%14 paired games

Erilium2 games · 13.3% of games in this matchup · Mean recorded OS 45.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.
Xad2 games · 13.3% of games in this matchup · Mean recorded OS 49.2Profile 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]Phoenix1 game · 6.7% 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.
[Crd]Atlas1 game · 6.7% of games in this matchup · Mean recorded OS 30.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]Thirsty_Shades1 game · 6.7% of games in this matchup · Mean recorded OS 15.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.
AcquiredTaste1 game · 6.7% of games in this matchup · Mean recorded OS 30.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.
bentheninja2244661 game · 6.7% of games in this matchup · Mean recorded OS 29.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.
BM_akumar61 game · 6.7% of games in this matchup · Mean recorded OS 43.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.
CentientWaffle1 game · 6.7% of games in this matchup · Mean recorded OS 31.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.
Dalekwithapipe1 game · 6.7% of games in this matchup · Mean recorded OS 10.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.
dp10001 game · 6.7% of games in this matchup · Mean recorded OS 23.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.
DRM1 game · 6.7% of games in this matchup · Mean recorded OS 44.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.
eichelMeister1 game · 6.7% of games in this matchup · Mean recorded OS 26.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.
heihallo1 game · 6.7% of games in this matchup · Mean recorded OS 28.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 · 6.7% of games in this matchup · Mean recorded OS 45.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 · 6.7% of games in this matchup · Mean recorded OS 32.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.
JesusIsGod1 game · 6.7% of games in this matchup · Mean recorded OS 18.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.
JumboJimbo1 game · 6.7% of games in this matchup · Mean recorded OS 27.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.
KingBenjai1 game · 6.7% of games in this matchup · Mean recorded OS 45.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.
kyoosh1 game · 6.7% of games in this matchup · Mean recorded OS 19.9Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.

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

Showing 20 of 28 recorded opponents.

Front (suicide) vs Shared central front · shared frontline

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

Average economy and combat

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
Measurement	Profile owner	Starting-lane opponents (per player)	Coverage
Metal producedTotal metal produced by this player by this time.	4,222.9 metal	3,807.2 metal	100.0%15 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.	4,714.1 metal	4,245.9 metal	100.0%15 paired games
Energy producedTotal energy produced by this player by this time.	47,495.7 energy	46,143.3 energy	100.0%15 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.	13,965.8 damage	9,408.5 damage	100.0%15 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.	13,480.0 damage	10,928.8 damage	100.0%15 paired games
Units producedTotal units produced by this time, including buildings.	49.7 units	46.2 units	100.0%15 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.	15.0 units	14.8 units	66.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.	1,810.2 metal	1,530.1 metal	93.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,474.4 metal	1,353.5 metal	93.3%14 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.	5.5 units	7.5 units	93.3%14 paired games

_X_2 games · 13.3% of games in this matchup · Mean recorded OS 47.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.
Hersch2 games · 13.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.
[Crd]Atlas1 game · 6.7% of games in this matchup · Mean recorded OS 30.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]NI_ILL1 game · 6.7% of games in this matchup · Mean recorded OS 28.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]Noodles1 game · 6.7% of games in this matchup · Mean recorded OS 28.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.
Blover1 game · 6.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.
CentientWaffle1 game · 6.7% of games in this matchup · Mean recorded OS 31.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.
chendashuai1 game · 6.7% of games in this matchup · Mean recorded OS 20.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.
clayton761 game · 6.7% of games in this matchup · Mean recorded OS 9.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.
Damsko1 game · 6.7% of games in this matchup · Mean recorded OS 40.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.
Deathkebab1 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.
FIynn1 game · 6.7% 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.
FrontLiner69er1 game · 6.7% of games in this matchup · Mean recorded OS 29.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.
GeeGee1 game · 6.7% of games in this matchup · Mean recorded OS 36.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.
Giverrion1 game · 6.7% of games in this matchup · Mean recorded OS 12.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.
Haddad1 game · 6.7% of games in this matchup · Mean recorded OS 11.8Profile owner’s team won 100.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
Hunfore1 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.
Immort1 game · 6.7% of games in this matchup · Mean recorded OS 55.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.
ITz_HonestAbee1 game · 6.7% 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.
ladenredan1 game · 6.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.

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.

Why some selected games have no identified lane:

No individual lane assigned for this position: 27 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.

Geo tech

Supreme Isthmus v2.1 · Large teams · 16 players

56.8 / 100

16 scored games · 84.2% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 60.3 recent vs 60.1 earlier, split at 13 Sep 2026. Approximate change range: -8.7 to 13.6 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

53.8 / 100

13 scored games · 92.9% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 55.6 recent vs 57.1 earlier, split at 16 Sep 2026. Approximate change range: -26.0 to 36.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

57.0 / 100

9 scored games · 64.3% coverage.

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

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

Why this score?

Pond

Supreme Isthmus v2.1 · Large teams · 16 players

49.2 / 100

5 scored games · 71.4% 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:46 UTC.

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

Air

1 selected games

More measured games are needed for traits.

Explore this position

Pond

7 selected games

More measured games are needed for traits.

Explore this position

Front (suicide)

13 selected games

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

Games with measurements for this trait: 84.6%.

Opens with Tick 76.9%

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

Front (second)

14 selected games

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

Geo tech

16 selected games

Opens with Bot Lab 93.8%

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

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: 95 published games lasting at least five minutes, linked to account 247228. 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: 96.8% 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.