Supreme Isthmus v2.1
73.3% of recorded games · 74 games
Tech25.7%
Air24.3%
Geo tech23.0%
Front (suicide)10.8%
Player profile · Account 82637
alexandar
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 25 Sep 2026 · Large teams · 16 players
- Recorded games
- 101 30 Aug 2026–25 Sep 2026 UTC
- Maps played
- 3 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.
152026-09-05
to 2026-09-11
to 2026-09-11
222026-09-12
to 2026-09-18
to 2026-09-18
342026-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.
All That Glitters v2.2.3
25.7% of recorded games · 26 games
Tech · P3 / P1130.8%
Carry · P7 / P1526.9%
Rainbow · P6 / P1411.5%
Bismuth Valley v2.4.1
1.0% of recorded games · 1 games
Front · P8100.0%
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: 20.3% of selected games.
Selected games: 74 · Games with identified lanes: 15.
24 distinct recorded opponents · Mean opponent OS 26.4 (OS available in 100.0% of identified games).
Beach sea vs Geo sea
4 matched games · 4 distinct opponents · Mean opponent OS 37.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.
4 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,809.4 metal | 3,936.1 metal | 100.0%4 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,429.7 metal | 4,593.9 metal | 100.0%4 paired games |
| Energy producedTotal energy produced by this player by this time. | 44,239.6 energy | 46,476.7 energy | 100.0%4 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 2,058.3 damage | 3,061.3 damage | 100.0%4 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 3,201.8 damage | 2,161.5 damage | 100.0%4 paired games |
| Units producedTotal units produced by this time, including buildings. | 36.5 units | 43.0 units | 100.0%4 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 4.5 units | 4.5 units | 50.0%2 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. | 418.0 metal | 380.8 metal | 100.0%4 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. | 315.8 metal | 396.5 metal | 100.0%4 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 2.0 units | 2.5 units | 100.0%4 paired games |
- 255ping1 game · 25.0% of games in this matchup · Mean recorded OS 19.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.
- _X_1 game · 25.0% of games in this matchup · Mean recorded OS 43.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.
- Alphacure1 game · 25.0% 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.
- Immort1 game · 25.0% of games in this matchup · Mean recorded OS 51.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
1 matched game · 2 distinct opponents · Mean opponent OS 26.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.
For shared Front, the opponent average is per opposing player in each game, and both opposing players must have records.
1 game 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. | 2,317.4 metal | 4,416.2 metal | 100.0%1 paired game |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 3,345.8 metal | 4,551.4 metal | 100.0%1 paired game |
| Energy producedTotal energy produced by this player by this time. | 52,484.3 energy | 43,051.4 energy | 100.0%1 paired game |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 8,332.6 damage | 9,183.4 damage | 100.0%1 paired game |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 15,327.7 damage | 11,097.9 damage | 100.0%1 paired game |
| Units producedTotal units produced by this time, including buildings. | 39.0 units | 39.0 units | 100.0%1 paired game |
| 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,601.0 metal | 704.0 metal | 100.0%1 paired game |
| 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. | 868.0 metal | 875.5 metal | 100.0%1 paired game |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 13.0 units | 6.5 units | 100.0%1 paired game |
- XNON1 game · 100.0% of games in this matchup · Mean recorded OS 22.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.
- XXMACGAMERXX1 game · 100.0% of games in this matchup · Mean recorded OS 30.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%.
Front (suicide) vs Shared central front · shared frontline
8 matched games · 16 distinct opponents · Mean opponent OS 24.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.
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. | 3,768.1 metal | 4,013.9 metal | 100.0%8 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,606.0 metal | 4,410.6 metal | 100.0%8 paired games |
| Energy producedTotal energy produced by this player by this time. | 56,997.8 energy | 46,102.5 energy | 100.0%8 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 12,481.0 damage | 10,609.2 damage | 100.0%8 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 13,601.1 damage | 12,073.9 damage | 100.0%8 paired games |
| Units producedTotal units produced by this time, including buildings. | 49.9 units | 45.6 units | 100.0%8 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 19.5 units | 12.2 units | 75.0%6 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,830.6 metal | 1,431.4 metal | 87.5%7 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,681.6 metal | 1,400.3 metal | 87.5%7 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 11.6 units | 7.9 units | 87.5%7 paired games |
- [Crd]DeAnthony1 game · 12.5% of games in this matchup · Mean recorded OS 19.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.
- AbyssFalcon1 game · 12.5% of games in this matchup · Mean recorded OS 30.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.
- aeroplane1 game · 12.5% of games in this matchup · Mean recorded OS 23.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.
- annie_may_tydease1 game · 12.5% of games in this matchup · Mean recorded OS 30.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.
- Anthrozil471 game · 12.5% of games in this matchup · Mean recorded OS 21.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.
- FrontLiner69er1 game · 12.5% of games in this matchup · Mean recorded OS 29.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.
- geogy1 game · 12.5% of games in this matchup · Mean recorded OS 22.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.
- gering1 game · 12.5% of games in this matchup · Mean recorded OS 10.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.
- JYHAK1 game · 12.5% 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.
- olozz721 game · 12.5% of games in this matchup · Mean recorded OS 10.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.
- polly3011 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
- Rde1 game · 12.5% of games in this matchup · Mean recorded OS 23.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.
- ReduceReclaimRez1 game · 12.5% 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.
- xabre1 game · 12.5% of games in this matchup · Mean recorded OS 47.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.
- YTnoat1201 game · 12.5% of games in this matchup · Mean recorded OS 16.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.
- Zetherite1 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
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
2 matched games · 2 distinct opponents · Mean opponent OS 13.4.
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.
2 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,976.3 metal | 2,993.2 metal | 100.0%2 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,797.7 metal | 3,484.1 metal | 100.0%2 paired games |
| Energy producedTotal energy produced by this player by this time. | 63,346.8 energy | 32,412.1 energy | 100.0%2 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 58.1 damage | 727.3 damage | 100.0%2 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 0.0 damage | 1,210.6 damage | 100.0%2 paired games |
| Units producedTotal units produced by this time, including buildings. | 44.0 units | 37.0 units | 100.0%2 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 2.0 units | 7.0 units | 50.0%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. | 25.5 metal | 206.5 metal | 100.0%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. | 36.5 metal | 118.5 metal | 100.0%2 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.5 units | 100.0%2 paired games |
- AngryTheGnome1 game · 50.0% of games in this matchup · Mean recorded OS 14.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.
- Whittle1 game · 50.0% of games in this matchup · Mean recorded OS 12.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.
Why some selected games have no identified lane:
- No individual lane assigned for this position: 59 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.
Geo sea
More measured games are needed for traits.
Explore this positionTech
Opens with Bot Lab 90.0%
Explore this positionThe 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 90% 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%.Air
Opens with Valiant 84.6%
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. Valiant was the first observed fighting unit start by 5:00 in 84.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%.Pond
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
Opens with Bot Lab 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%.Defence-heavy opening 90.0%
Explore this positionBy 5:00, fixed defences represent at least 60% of completed military build value in at least 70% of at least 10 measured games. This is normal build value, not personal spending. Fixed defences reached at least 60% of completed military build value by 5:00 in 90% of measured games. The denominator includes completed fighting units and fixed defences, including builds later lost; unfinished work is excluded.
Games with measurements for this trait: 66.7%.Beach sea
More measured games are needed for traits.
Explore this positionAsk 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: 101 published games lasting at least five minutes, linked to account 82637. 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: 89.1% 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:41 UTC; this summary prepared 02 Oct 2026, 10:57 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.