Supreme Isthmus v2.1
14 games20.6% of recorded games
Spurgeon_Tanner
Account 609997 · Published replay history across maps and positions.
- Latest recorded OS
- 19.5 13 Aug 2026 · Duel · 2 players
- Recorded games
- 68 03 Jul 2026–13 Aug 2026 UTC
- Maps played
- 32 Map versions counted separately
OS over time
Ratings recorded at game start in the replays we have. OS means OpenSkill rating.
- First recorded
- 26.80
- Latest recorded
- 19.46
- Change
- -7.34
13 Aug 2026, 12:26 UTC · OS 19.46
37 recorded ratings · 29 Jul 2026–13 Aug 2026.
Game formats are shown separately.
Playstyle and score by position
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.
No habits to show yet. Habits come from Supreme Isthmus v2.1 human 8v8 games between 15 Sep and 14 Oct 2026 (UTC), with at least 10 measured games in a position. This player has none in that period.
Recent activity
Recorded games in the last four weeks. This shows activity, not a change in skill. Imports may be incomplete.
02026-09-17
to 2026-09-23
to 2026-09-23
02026-09-24
to 2026-09-30
to 2026-09-30
02026-10-01
to 2026-10-07
to 2026-10-07
02026-10-08
to 2026-10-14
to 2026-10-14
Most played maps & positions
Share of this player’s published games. Starting positions describe where they began; responsibilities can change during play.
Avalanche 3.4
5 games7.4% of recorded games
Canis River v1.4
5 games7.4% of recorded games
Onyx Cauldron 2.2.2
4 games5.9% of recorded games
Ravaged Remake v1.2
4 games5.9% of recorded games
Comet Catcher Remake 1.8
3 games4.4% of recorded games
Isidis crack 1.1
3 games4.4% of recorded games
Quicksilver Remake 1.24
3 games4.4% of recorded games
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: 78.6% of selected games.
Selected games: 14 · Games with identified lanes: 11.
20 distinct recorded opponents · Mean opponent OS 12.6 (OS available in 100.0% of identified games).
Front (second) vs Shared central front · shared frontline
8 matched games · 14 distinct opponents · Mean opponent OS 13.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 →
| Measurement | Profile owner | Starting-lane opponents (per player) | Coverage |
|---|---|---|---|
| Metal producedTotal metal produced by this player by this time. | 4,053.6 metal | 3,992.0 metal | 100.0%8 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,134.5 metal | 4,335.0 metal | 100.0%8 paired games |
| Energy producedTotal energy produced by this player by this time. | 36,276.6 energy | 47,390.3 energy | 100.0%8 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 7,138.6 damage | 9,525.1 damage | 100.0%8 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 7,755.7 damage | 8,621.0 damage | 100.0%8 paired games |
| Units producedTotal units produced by this time, including buildings. | 41.4 units | 45.2 units | 100.0%8 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. | Not recorded | Not recorded | 0.0%0 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. | Not recorded | Not recorded | 0.0%0 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | Not recorded | Not recorded | 0.0%0 paired games |
- longsongzlc2 games · 25.0% of games in this matchup · Mean recorded OS 10.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.
- sunflower9647952 games · 25.0% 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.
- _Poseidon_1 game · 12.5% 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.
- Bazdah1 game · 12.5% of games in this matchup · Mean recorded OS 19.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.
- Brandin1 game · 12.5% of games in this matchup · Mean recorded OS 7.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.
- Colibriii1 game · 12.5% of games in this matchup · Mean recorded OS 9.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.
- Colonel_jojinskii1 game · 12.5% of games in this matchup · Mean recorded OS 12.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.
- fulmucos1 game · 12.5% of games in this matchup · Mean recorded OS 23.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.
- Glassadder1 game · 12.5% of games in this matchup · Mean recorded OS 9.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.
- Herpes_Harry1 game · 12.5% of games in this matchup · Mean recorded OS 5.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.
- LaDenree1 game · 12.5% of games in this matchup · Mean recorded OS 15.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.
- LagnaLoki1 game · 12.5% of games in this matchup · Mean recorded OS 12.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.
- Remelord1 game · 12.5% of games in this matchup · Mean recorded OS 7.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.
- Tyrygosa1 game · 12.5% of games in this matchup · Mean recorded OS 17.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.
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
3 matched games · 6 distinct opponents · Mean opponent OS 11.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.
For shared Front, the opponent average is per opposing player in each game, and both opposing players must have records.
3 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. | 4,699.9 metal | 3,394.5 metal | 100.0%3 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,230.7 metal | 3,816.4 metal | 100.0%3 paired games |
| Energy producedTotal energy produced by this player by this time. | 41,931.6 energy | 47,514.8 energy | 100.0%3 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 8,134.2 damage | 7,423.1 damage | 100.0%3 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 12,915.1 damage | 12,854.0 damage | 100.0%3 paired games |
| Units producedTotal units produced by this time, including buildings. | 50.0 units | 44.0 units | 100.0%3 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. | Not recorded | Not recorded | 0.0%0 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. | Not recorded | Not recorded | 0.0%0 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | Not recorded | Not recorded | 0.0%0 paired games |
- Knizek1 game · 33.3% of games in this matchup · Mean recorded OS 15.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.
- m4rvinbot1 game · 33.3% of games in this matchup · Mean recorded OS 6.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.
- PlsNerfMee1 game · 33.3% of games in this matchup · Mean recorded OS 11.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.
- PuLSor24_1 game · 33.3% of games in this matchup · Mean recorded OS 11.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.
- ScruffyGuff1 game · 33.3% 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.
- steveirwin81 game · 33.3% of games in this matchup · Mean recorded OS 4.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.
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%.
Why some selected games have no identified lane:
- Starting layout not verified: 2 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.
Ask about this player
Open a prepared question for Supreme Isthmus v2.1, then adjust the map, position, game version or reference rating.
About these results
Included: 68 published games lasting at least five minutes, linked to account 609997. 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: 100.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 14 Oct 2026, 09:22 UTC; this summary prepared 14 Oct 2026, 09:56 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.