Supreme Isthmus v2.1
98.7% of recorded games · 148 games
Player profile · Account 260642
A quick view of this player’s published replay history. Choose a map below to explore their play in more detail.
Recorded games in the last four weeks. This shows activity, not a change in skill. Imports may be incomplete.
Share of this player’s published games. Starting positions describe where they began; responsibilities can change during play.
98.7% of recorded games · 148 games
0.7% of recorded games · 1 games
0.7% of recorded games · 1 games
Supreme Isthmus v2.1 human 8v8 starting lanes. This shows fixed opposing starts, not every opponent who later joined a fight.
Starting-lane coverage: 40.7% of selected games.
Selected games: 145 · Games with identified lanes: 59.
58 distinct recorded opponents · Mean opponent OS 36.7 (OS available in 100.0% of identified games).
3 matched games · 3 distinct opponents · Mean opponent OS 39.9.
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.
3 games reached 5:00.
Swipe sideways to compare both sides →
| Measurement | Profile owner | Starting-lane opponent | Coverage |
|---|---|---|---|
| Metal producedTotal metal produced by this player by this time. | 3,445.2 metal | 3,716.2 metal | 100.0%3 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,154.8 metal | 4,376.8 metal | 100.0%3 paired games |
| Energy producedTotal energy produced by this player by this time. | 35,754.9 energy | 44,836.8 energy | 100.0%3 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 2,490.4 damage | 1,980.5 damage | 100.0%3 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 2,089.3 damage | 2,471.9 damage | 100.0%3 paired games |
| Units producedTotal units produced by this time, including buildings. | 33.3 units | 36.3 units | 100.0%3 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 2.0 units | 7.0 units | 33.3%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. | 520.5 metal | 164.0 metal | 66.7%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. | 174.0 metal | 547.0 metal | 66.7%2 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 1.0 units | 0.5 units | 66.7%2 paired games |
26 matched games · 39 distinct opponents · Mean opponent OS 40.0.
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.
26 games reached 5:00.
Swipe sideways to compare both sides →
| Measurement | Profile owner | Starting-lane opponents (per player) | Coverage |
|---|---|---|---|
| Metal producedTotal metal produced by this player by this time. | 3,641.4 metal | 3,849.1 metal | 100.0%26 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,383.3 metal | 4,452.9 metal | 100.0%26 paired games |
| Energy producedTotal energy produced by this player by this time. | 45,963.1 energy | 45,818.4 energy | 100.0%26 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 11,290.9 damage | 11,612.2 damage | 100.0%26 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 9,360.8 damage | 12,863.1 damage | 100.0%26 paired games |
| Units producedTotal units produced by this time, including buildings. | 42.1 units | 46.1 units | 100.0%26 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 6.3 units | 9.2 units | 11.5%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. | 793.8 metal | 1,343.0 metal | 96.2%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. | 1,240.0 metal | 993.0 metal | 96.2%25 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 5.8 units | 7.9 units | 96.2%25 paired games |
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 39 recorded opponents.
30 matched games · 25 distinct opponents · Mean opponent OS 33.4.
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.
30 games reached 5:00.
Swipe sideways to compare both sides →
| Measurement | Profile owner | Starting-lane opponent | Coverage |
|---|---|---|---|
| Metal producedTotal metal produced by this player by this time. | 4,050.6 metal | 3,569.6 metal | 100.0%30 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 5,027.6 metal | 4,108.3 metal | 100.0%30 paired games |
| Energy producedTotal energy produced by this player by this time. | 47,306.2 energy | 35,461.2 energy | 100.0%30 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 1,338.4 damage | 1,590.4 damage | 100.0%30 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 1,257.3 damage | 1,422.9 damage | 100.0%30 paired games |
| Units producedTotal units produced by this time, including buildings. | 38.5 units | 32.2 units | 100.0%30 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 2.9 units | 2.6 units | 33.3%10 paired games |
| Metal lost to enemiesMetal cost of completed units and buildings lost to enemies by this time. Includes commanders; excludes unfinished units and reclaim. Wreckage recovered later is not subtracted. | 139.0 metal | 192.5 metal | 83.3%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. | 186.3 metal | 281.9 metal | 83.3%25 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 0.7 units | 0.6 units | 83.3%25 paired games |
Showing 20 of 25 recorded opponents.
Why some selected games have no identified lane:
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.
Prepared ranking results, with the same calculation and evidence as the rankings page. Scores are not OS or a share of team victory.
56.3 / 100
Why this score?51.8 / 100
Why this score?57.7 / 100
Why this score?47.6 / 100
Why this score?52.2 / 100
Why this score?52.3 / 100
Why this score?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.
These traits are awaiting a refresh. They describe the period printed above.
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 86.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%.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%.By 15:00, finished more bombers than both the matching group’s average and its 75th percentile (the cutoff for the top quarter). This must happen in at least 60% of at least 10 games with data. Building bombers does not prove a bombing run happened. Above both comparison cutoffs in 60% of matching games with data at 15:00. Matching comparison games available for 66.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: 45.5%.By 10:00, finished fewer fighters than both the matching group’s average and its 25th percentile (the cutoff for the bottom quarter). This must happen in at least 60% of at least 10 games with data. It describes building habits, not whether the player controlled the air or used resources well. Below both comparison cutoffs in 64.3% of matching games with data at 10:00. Matching comparison games available for 66.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: 63.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 63.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%.Common teammate unit transfers while playing Pond. These may include gifts; payment is not recorded. Advanced Construction Bot received from a teammate by 10:00 in 92% of observed Pond games (12 games with complete data). Finished at receipt in 58%; unfinished in 33% (these can overlap). Gifts are included; payment is not recorded.
Games with measurements for this trait: 80.0%.Common teammate unit transfers while playing Pond. These may include gifts; payment is not recorded. Fatboy received from a teammate by 10:00 in 67% of observed Pond games (12 games with complete data). Finished at receipt in 25%; unfinished in 42% (these can overlap). Gifts are included; payment is not recorded.
Games with measurements for this trait: 80.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. Vehicle Plant was the first observed factory 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%.The same first observed fighting unit start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Rover was the first observed fighting unit start by 5:00 in 87.5% 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%.More measured games are needed for traits.
Explore this positionMore measured games are needed for traits.
Explore this positionOpen a prepared question for the most played map, then adjust the map, position, game version or reference rating.
Included: 150 published games lasting at least five minutes, linked to account 260642. 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.0% 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.