Supreme Isthmus v2.1
100.0% of recorded games · 47 games
Beach sea38.3%
Geo sea34.0%
Air6.4%
Front (suicide)6.4%
Player profile · Account 99175
Askol_d
A quick view of this player’s published replay history. Choose a map below to explore their play in more detail.
- Latest recorded OS
- 25.2 13 Sep 2026 · Large teams · 16 players
- Recorded games
- 47 30 Aug 2026–13 Sep 2026 UTC
- Maps played
- 1 Map versions counted separately
Recent activity
Recorded games in the last four weeks. This shows activity, not a change in skill. Imports may be incomplete.
252026-09-05
to 2026-09-11
to 2026-09-11
52026-09-12
to 2026-09-18
to 2026-09-18
02026-09-19
to 2026-09-25
to 2026-09-25
02026-09-26
to 2026-10-02
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.
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: 80.8% of selected games.
Selected games: 47 · Games with identified lanes: 38.
39 distinct recorded opponents · Mean opponent OS 23.8 (OS available in 100.0% of identified games).
Beach sea vs Geo sea
16 matched games · 14 distinct opponents · Mean opponent OS 21.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.
16 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,337.1 metal | 3,803.8 metal | 100.0%16 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 3,801.7 metal | 4,326.3 metal | 100.0%16 paired games |
| Energy producedTotal energy produced by this player by this time. | 37,709.2 energy | 48,758.3 energy | 100.0%16 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 631.5 damage | 427.0 damage | 100.0%16 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 502.2 damage | 433.6 damage | 100.0%16 paired games |
| Units producedTotal units produced by this time, including buildings. | 33.1 units | 40.3 units | 100.0%16 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. | 97.8 metal | 95.6 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. | 177.8 metal | 90.6 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. | 0.1 units | 0.1 units | 100.0%16 paired games |
- KoolAid2 games · 12.5% of games in this matchup · Mean recorded OS 10.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.
- Slow_but_sure2 games · 12.5% of games in this matchup · Mean recorded OS 27.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.
- AcOrP1 game · 6.2% of games in this matchup · Mean recorded OS 28.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.
- Apachon1 game · 6.2% of games in this matchup · Mean recorded OS 14.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.
- ChickenMan2771 game · 6.2% of games in this matchup · Mean recorded OS 24.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.
- El_Turco1 game · 6.2% of games in this matchup · Mean recorded OS 29.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.
- FrugalResources1 game · 6.2% of games in this matchup · Mean recorded OS 30.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.
- Glassadder1 game · 6.2% 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.
- HorseWalksIntoABAR1 game · 6.2% of games in this matchup · Mean recorded OS 12.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.
- IMBALANCED1 game · 6.2% of games in this matchup · Mean recorded OS 41.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.
- JesterB1 game · 6.2% of games in this matchup · Mean recorded OS 35.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.
- magicleo1 game · 6.2% of games in this matchup · Mean recorded OS 16.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.
- Nulin1 game · 6.2% of games in this matchup · Mean recorded OS 13.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.
- postmortem1 game · 6.2% 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.
Front (second) vs Shared central front · shared frontline
3 matched games · 6 distinct opponents · Mean opponent OS 27.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.
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. | 3,626.6 metal | 4,112.4 metal | 100.0%3 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,497.8 metal | 4,479.6 metal | 100.0%3 paired games |
| Energy producedTotal energy produced by this player by this time. | 52,688.6 energy | 53,086.8 energy | 100.0%3 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 9,290.7 damage | 11,046.4 damage | 100.0%3 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 10,667.3 damage | 10,051.4 damage | 100.0%3 paired games |
| Units producedTotal units produced by this time, including buildings. | 47.0 units | 46.8 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. | 1,659.7 metal | 696.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. | 401.7 metal | 1,475.3 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. | 7.7 units | 6.0 units | 100.0%3 paired games |
- Bishtou1 game · 33.3% of games in this matchup · Mean recorded OS 26.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.
- heart_attack1 game · 33.3% of games in this matchup · Mean recorded OS 35.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.
- JantDarvus1 game · 33.3% of games in this matchup · Mean recorded OS 25.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.
- Mrniceguy20231 game · 33.3% of games in this matchup · Mean recorded OS 26.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.
- speddyteddy1 game · 33.3% of games in this matchup · Mean recorded OS 31.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.
- TheMP1 game · 33.3% 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.
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 21.0.
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,073.0 metal | 4,146.7 metal | 100.0%3 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 3,980.5 metal | 4,579.7 metal | 100.0%3 paired games |
| Energy producedTotal energy produced by this player by this time. | 38,952.4 energy | 41,983.4 energy | 100.0%3 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 6,948.9 damage | 8,650.1 damage | 100.0%3 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 9,573.1 damage | 6,515.5 damage | 100.0%3 paired games |
| Units producedTotal units produced by this time, including buildings. | 43.7 units | 48.2 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. | 1,347.7 metal | 900.2 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. | 1,249.7 metal | 1,168.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. | 11.7 units | 4.5 units | 100.0%3 paired games |
- [BS]RohNiN1 game · 33.3% of games in this matchup · Mean recorded OS 38.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.
- DeGufis1 game · 33.3% 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.
- iGhost1 game · 33.3% 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.
- magicleo1 game · 33.3% of games in this matchup · Mean recorded OS 16.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.
- Rde1 game · 33.3% of games in this matchup · Mean recorded OS 25.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.
- TheDankOne1 game · 33.3% of games in this matchup · Mean recorded OS 17.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.
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%.
Geo sea vs Beach sea
16 matched games · 16 distinct opponents · Mean opponent OS 25.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.
16 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,722.8 metal | 3,602.1 metal | 100.0%16 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,308.5 metal | 4,146.4 metal | 100.0%16 paired games |
| Energy producedTotal energy produced by this player by this time. | 56,049.8 energy | 40,801.9 energy | 100.0%16 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 304.9 damage | 1,174.7 damage | 100.0%16 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 883.2 damage | 537.8 damage | 100.0%16 paired games |
| Units producedTotal units produced by this time, including buildings. | 43.4 units | 35.2 units | 100.0%16 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. | 105.6 metal | 131.1 metal | 93.8%15 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. | 88.3 metal | 161.3 metal | 93.8%15 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.5 units | 93.8%15 paired games |
- [BS]Phoenix1 game · 6.2% of games in this matchup · Mean recorded OS 30.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.
- Akuji1 game · 6.2% 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.
- arcsiz1 game · 6.2% of games in this matchup · Mean recorded OS 35.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.
- AzurePure1 game · 6.2% of games in this matchup · Mean recorded OS 21.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.
- badbot1 game · 6.2% of games in this matchup · Mean recorded OS 33.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.
- D4rkF0restTheory1 game · 6.2% of games in this matchup · Mean recorded OS 22.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.
- Disgraceful1 game · 6.2% of games in this matchup · Mean recorded OS 22.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.
- haaven1 game · 6.2% of games in this matchup · Mean recorded OS 44.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.
- hido1 game · 6.2% 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.
- iGhost1 game · 6.2% 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.
- Immort1 game · 6.2% of games in this matchup · Mean recorded OS 52.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.
- JesterB1 game · 6.2% of games in this matchup · Mean recorded OS 34.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.
- megasopeda1 game · 6.2% of games in this matchup · Mean recorded OS 11.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.
- Ochumecha1 game · 6.2% of games in this matchup · Mean recorded OS 16.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.
- semitacbattlefat1 game · 6.2% of games in this matchup · Mean recorded OS 16.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.
- Tres1 game · 6.2% of games in this matchup · Mean recorded OS 18.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.
Why some selected games have no identified lane:
- No individual lane assigned for this position: 7 games.
- Starting-position records unavailable: 2 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.
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.
These traits are awaiting a refresh. They describe the period printed above.
Geo sea
Opens with Trasher 92.9%
Explore this positionThe 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. Trasher was the first observed fighting unit start by 5:00 in 92.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%.Tech
More measured games are needed for traits.
Explore this positionAir
More measured games are needed for traits.
Explore this positionFront (suicide)
More measured games are needed for traits.
Explore this positionFront (second)
More measured games are needed for traits.
Explore this positionGeo tech
More measured games are needed for traits.
Explore this positionBeach sea
Riptide-heavy by 10:00 61.5%
By 10:00, completed at least 5 Riptide 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 61.5% of comparable measured games. Average built in games with data: 5.87 Riptide units by 10:00.
Games with measurements for this trait: 76.5%.Opens with Herring 82.4%
Explore this positionThe 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. Herring was the first observed fighting unit start by 5:00 in 82.4% 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%.Ask about this player
Open a prepared question for the most played map, then adjust the map, position, game version or reference rating.
About these results
Included: 47 published games lasting at least five minutes, linked to account 99175. 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 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.