Supreme Isthmus v2.1
100.0% of recorded games · 96 games
Geo sea51.0%
Tech21.9%
Geo tech9.4%
Pond5.2%
Player profile · Account 363577
Alphacure
A quick view of this player’s published replay history. Choose a map below to explore their play in more detail.
- Latest recorded OS
- 38.2 29 Sep 2026 · Large teams · 16 players
- Recorded games
- 96 30 Aug 2026–29 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.
182026-09-05
to 2026-09-11
to 2026-09-11
152026-09-12
to 2026-09-18
to 2026-09-18
322026-09-19
to 2026-09-25
to 2026-09-25
192026-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: 56.2% of selected games.
Selected games: 96 · Games with identified lanes: 54.
54 distinct recorded opponents · Mean opponent OS 22.8 (OS available in 100.0% of identified games).
Beach sea vs Geo sea
1 matched game · 1 distinct opponent · Mean opponent OS 30.9.
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.
1 game 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,130.4 metal | 4,240.5 metal | 100.0%1 paired game |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 3,792.8 metal | 4,547.4 metal | 100.0%1 paired game |
| Energy producedTotal energy produced by this player by this time. | 23,586.1 energy | 46,492.4 energy | 100.0%1 paired game |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 6,877.4 damage | 4,911.9 damage | 100.0%1 paired game |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 3,980.1 damage | 7,819.2 damage | 100.0%1 paired game |
| Units producedTotal units produced by this time, including buildings. | 27.0 units | 36.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. | 720.0 metal | 821.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. | 770.0 metal | 793.0 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. | 2.0 units | 0.0 units | 100.0%1 paired game |
- Hello_World1 game · 100.0% of games in this matchup · Mean recorded OS 30.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.
Front (second) vs Shared central front · shared frontline
4 matched games · 8 distinct opponents · Mean opponent OS 20.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.
4 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,264.4 metal | 3,668.2 metal | 100.0%4 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,390.3 metal | 4,339.2 metal | 100.0%4 paired games |
| Energy producedTotal energy produced by this player by this time. | 51,494.8 energy | 44,024.1 energy | 100.0%4 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 12,920.4 damage | 7,516.0 damage | 100.0%4 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 8,518.9 damage | 11,798.3 damage | 100.0%4 paired games |
| Units producedTotal units produced by this time, including buildings. | 41.0 units | 45.6 units | 100.0%4 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. | 355.0 metal | 1,158.1 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. | 1,158.5 metal | 377.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. | 5.2 units | 8.6 units | 100.0%4 paired games |
- [I]_[I]1 game · 25.0% of games in this matchup · Mean recorded OS 10.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 · 25.0% of games in this matchup · Mean recorded OS 21.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.
- Boden1 game · 25.0% of games in this matchup · Mean recorded OS 17.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.
- halconcito1 game · 25.0% of games in this matchup · Mean recorded OS 16.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.
- Litonel1 game · 25.0% of games in this matchup · Mean recorded OS 16.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.
- officialjurq1 game · 25.0% of games in this matchup · Mean recorded OS 23.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.
- Typasius1 game · 25.0% of games in this matchup · Mean recorded OS 24.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.
- XXMACGAMERXX1 game · 25.0% of games in this matchup · Mean recorded OS 34.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.
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
1 matched game · 2 distinct opponents · Mean opponent OS 30.7.
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. | 3,435.4 metal | 4,207.2 metal | 100.0%1 paired game |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,340.0 metal | 4,757.0 metal | 100.0%1 paired game |
| Energy producedTotal energy produced by this player by this time. | 42,478.4 energy | 49,415.5 energy | 100.0%1 paired game |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 17,324.4 damage | 11,668.6 damage | 100.0%1 paired game |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 16,051.4 damage | 15,072.5 damage | 100.0%1 paired game |
| Units producedTotal units produced by this time, including buildings. | 45.0 units | 47.5 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. | 2,002.0 metal | 1,331.5 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. | 1,507.0 metal | 2,418.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 | 13.0 units | 100.0%1 paired game |
- field_marshal1 game · 100.0% of games in this matchup · Mean recorded OS 28.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.
- PrivatePershing1 game · 100.0% of games in this matchup · Mean recorded OS 32.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%.
Geo sea vs Beach sea
48 matched games · 44 distinct opponents · Mean opponent OS 22.6.
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.
48 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,219.1 metal | 3,528.9 metal | 100.0%48 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 5,058.8 metal | 4,137.1 metal | 100.0%48 paired games |
| Energy producedTotal energy produced by this player by this time. | 48,538.7 energy | 38,830.2 energy | 100.0%48 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 1,240.4 damage | 2,007.6 damage | 100.0%48 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 1,854.8 damage | 1,316.1 damage | 100.0%48 paired games |
| Units producedTotal units produced by this time, including buildings. | 42.9 units | 33.3 units | 100.0%48 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 2.9 units | 3.4 units | 29.2%14 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. | 177.9 metal | 222.8 metal | 89.6%43 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. | 200.3 metal | 228.6 metal | 89.6%43 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 0.2 units | 1.1 units | 89.6%43 paired games |
- Bestoloch3 games · 6.2% of games in this matchup · Mean recorded OS 30.5Profile owner’s team won 66.7% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
- ComDelivery2 games · 4.2% of games in this matchup · Mean recorded OS 38.4Profile 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.
- TTAC2 games · 4.2% of games in this matchup · Mean recorded OS 13.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.
- 124121 game · 2.1% of games in this matchup · Mean recorded OS 23.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.
- [BS]SimpleEconomyAI1 game · 2.1% of games in this matchup · Mean recorded OS 28.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.
- [Crd]DeAnthony1 game · 2.1% of games in this matchup · Mean recorded OS 17.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.
- [Crd]remk3631 game · 2.1% of games in this matchup · Mean recorded OS 19.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.
- [I]_[I]1 game · 2.1% of games in this matchup · Mean recorded OS 10.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.
- alexandar1 game · 2.1% of games in this matchup · Mean recorded OS 23.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.
- ArkAngel81 game · 2.1% of games in this matchup · Mean recorded OS 16.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.
- Bazdah1 game · 2.1% of games in this matchup · Mean recorded OS 25.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.
- cmilly1 game · 2.1% of games in this matchup · Mean recorded OS 15.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.
- Coordinate1 game · 2.1% of games in this matchup · Mean recorded OS 17.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.
- DanieI1 game · 2.1% of games in this matchup · Mean recorded OS 19.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.
- Dante0nline1 game · 2.1% of games in this matchup · Mean recorded OS 8.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.
- dasheino1 game · 2.1% of games in this matchup · Mean recorded OS 20.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.
- EdiK1 game · 2.1% of games in this matchup · Mean recorded OS 17.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.
- GravesGrace1 game · 2.1% of games in this matchup · Mean recorded OS 14.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.
- Grond_1 game · 2.1% of games in this matchup · Mean recorded OS 26.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.
- GryfH1 game · 2.1% of games in this matchup · Mean recorded OS 27.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.
Showing 20 of 44 recorded opponents.
Why some selected games have no identified lane:
- Starting layout not verified: 4 games.
- No individual lane assigned for this position: 37 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.
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
Submarine opener 73.9%
A submarine was the first completed naval combat unit by 5:00 in at least 40% of at least 10 measured openings. If several units finish first at the same time, all must be submarines. Games with no finished naval fighting units still count in the percentage. Gifts and free units do not count as builds. Submarine first in 73.9% of measured openings. This is a recurring opener, not a prediction of the current game.
Games with measurements for this trait: 100.0%.Opens with Trasher 67.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. Trasher was the first observed fighting unit start by 5:00 in 67.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%.Tech
Opens with Bot Lab 100.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 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%.Air
More measured games are needed for traits.
Explore this positionPond
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
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: 96 published games lasting at least five minutes, linked to account 363577. 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: 92.7% 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.