Supreme Isthmus v2.1
89.3% of recorded games · 92 games
Front (suicide)68.5%
Front (second)13.0%
Beach sea6.5%
Geo tech4.3%
Player profile · Account 359574
derkarl
A quick view of this player’s published replay history. Choose a map below to explore their play in more detail.
- Latest recorded OS
- 39.6 29 Sep 2026 · Large teams · 16 players
- Recorded games
- 103 30 Aug 2026–29 Sep 2026 UTC
- Maps played
- 12 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.
142026-09-05
to 2026-09-11
to 2026-09-11
182026-09-12
to 2026-09-18
to 2026-09-18
452026-09-19
to 2026-09-25
to 2026-09-25
222026-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.
Ascendancy v2.2
1.0% of recorded games · 1 games
Front · P9100.0%
Bismuth Valley v2.4.1
1.0% of recorded games · 1 games
Front · P1100.0%
Delta Siege Dry v5.7.1
1.0% of recorded games · 1 games
Front · P1100.0%
Failed Negotiations 1.0
1.0% of recorded games · 1 games
Front · P2 / P10100.0%
Forge v2.3
1.0% of recorded games · 1 games
Front · P16100.0%
Hades Ponds 1.1
1.0% of recorded games · 1 games
Front · P2 / P10100.0%
Hyperion Shale 1.0.2
1.0% of recorded games · 1 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: 85.9% of selected games.
Selected games: 92 · Games with identified lanes: 79.
124 distinct recorded opponents · Mean opponent OS 28.9 (OS available in 100.0% of identified games).
Beach sea vs Geo sea
6 matched games · 6 distinct opponents · Mean opponent OS 34.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.
6 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,613.4 metal | 3,944.9 metal | 100.0%6 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,240.3 metal | 4,957.1 metal | 100.0%6 paired games |
| Energy producedTotal energy produced by this player by this time. | 26,724.2 energy | 53,454.8 energy | 100.0%6 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 2,012.0 damage | 1,713.6 damage | 100.0%6 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 1,994.8 damage | 1,970.4 damage | 100.0%6 paired games |
| Units producedTotal units produced by this time, including buildings. | 28.3 units | 39.8 units | 100.0%6 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. | 484.2 metal | 180.3 metal | 100.0%6 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. | 204.0 metal | 429.3 metal | 100.0%6 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 1.3 units | 0.5 units | 100.0%6 paired games |
- AcquiredTaste1 game · 16.7% of games in this matchup · Mean recorded OS 30.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.
- Dad_The_Speedrunner1 game · 16.7% of games in this matchup · Mean recorded OS 33.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.
- Elpoloow1 game · 16.7% of games in this matchup · Mean recorded OS 34.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.
- I_pawngame_u1 game · 16.7% 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.
- SHOGVN1 game · 16.7% of games in this matchup · Mean recorded OS 37.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.
- sirniho1 game · 16.7% of games in this matchup · Mean recorded OS 38.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.
Front (second) vs Shared central front · shared frontline
10 matched games · 18 distinct opponents · Mean opponent OS 27.2.
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.
10 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,897.4 metal | 3,424.0 metal | 100.0%10 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,162.9 metal | 4,153.7 metal | 100.0%10 paired games |
| Energy producedTotal energy produced by this player by this time. | 44,291.6 energy | 47,094.0 energy | 100.0%10 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 11,434.9 damage | 10,898.5 damage | 100.0%10 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 9,759.2 damage | 14,127.5 damage | 100.0%10 paired games |
| Units producedTotal units produced by this time, including buildings. | 38.7 units | 45.8 units | 100.0%10 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 10.0 units | 19.5 units | 10.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. | 1,252.1 metal | 2,181.4 metal | 100.0%10 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,879.5 metal | 1,187.4 metal | 100.0%10 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 9.4 units | 9.7 units | 100.0%10 paired games |
- Nooobbbys2 games · 20.0% of games in this matchup · Mean recorded OS 20.6Profile 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.
- Soliloqueur2 games · 20.0% of games in this matchup · Mean recorded OS 41.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.
- AcOrP1 game · 10.0% of games in this matchup · Mean recorded OS 24.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.
- Adeus1 game · 10.0% of games in this matchup · Mean recorded OS 36.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.
- BiteMyAssets1 game · 10.0% of games in this matchup · Mean recorded OS 30.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.
- Comas1 game · 10.0% of games in this matchup · Mean recorded OS 14.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.
- Dreadfire1 game · 10.0% of games in this matchup · Mean recorded OS 19.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.
- DrPhrogg1 game · 10.0% of games in this matchup · Mean recorded OS 10.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.
- El_Turco1 game · 10.0% of games in this matchup · Mean recorded OS 28.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.
- Erilium1 game · 10.0% of games in this matchup · Mean recorded OS 45.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.
- Hannodins1 game · 10.0% of games in this matchup · Mean recorded OS 35.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.
- Heuristic_Vigil1 game · 10.0% of games in this matchup · Mean recorded OS 23.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.
- Hunfore1 game · 10.0% of games in this matchup · Mean recorded OS 32.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.
- IceZin1 game · 10.0% of games in this matchup · Mean recorded OS 17.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.
- Jonjo_131 game · 10.0% of games in this matchup · Mean recorded OS 28.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.
- soteiru1 game · 10.0% of games in this matchup · Mean recorded OS 26.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.
- Tetrox1 game · 10.0% of games in this matchup · Mean recorded OS 15.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.
- thrashers731 game · 10.0% of games in this matchup · Mean recorded OS 28.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.
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
61 matched games · 106 distinct opponents · Mean opponent OS 28.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.
61 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,294.0 metal | 3,817.5 metal | 100.0%61 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 4,871.1 metal | 4,354.3 metal | 100.0%61 paired games |
| Energy producedTotal energy produced by this player by this time. | 51,523.5 energy | 48,299.3 energy | 100.0%61 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 16,256.4 damage | 10,522.9 damage | 100.0%61 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 13,856.7 damage | 12,435.5 damage | 100.0%61 paired games |
| Units producedTotal units produced by this time, including buildings. | 51.9 units | 45.8 units | 100.0%61 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 9.3 units | 13.2 units | 52.5%32 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. | 979.6 metal | 1,361.4 metal | 85.2%52 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,790.1 metal | 881.6 metal | 85.2%52 paired games |
| Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings. | 4.1 units | 7.7 units | 85.2%52 paired games |
- [Crd]Noodles3 games · 4.9% of games in this matchup · Mean recorded OS 28.4Profile 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.
- Concinus3 games · 4.9% of games in this matchup · Mean recorded OS 24.4Profile 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.
- DeathReaper9953 games · 4.9% of games in this matchup · Mean recorded OS 14.9Profile 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.
- Espera3 games · 4.9% of games in this matchup · Mean recorded OS 38.1Profile 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.
- Soliloqueur3 games · 4.9% of games in this matchup · Mean recorded OS 41.6Profile owner’s team won 33.3% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
- [AoW]Vritrasura2 games · 3.3% of games in this matchup · Mean recorded OS 24.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]Hellzie2 games · 3.3% of games in this matchup · Mean recorded OS 37.8Profile 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.
- [Crd]Atlas2 games · 3.3% of games in this matchup · Mean recorded OS 29.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.
- El_Turco2 games · 3.3% of games in this matchup · Mean recorded OS 30.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.
- Ganttura2 games · 3.3% of games in this matchup · Mean recorded OS 17.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.
- Immort2 games · 3.3% of games in this matchup · Mean recorded OS 54.0Profile 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.
- 0neTw01 game · 1.6% of games in this matchup · Mean recorded OS 40.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.
- [A7O]SuperTetra1 game · 1.6% of games in this matchup · Mean recorded OS 30.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.
- [CC]CupOfCoffee1 game · 1.6% of games in this matchup · Mean recorded OS 28.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.
- [Crd]ALRO1 game · 1.6% of games in this matchup · Mean recorded OS 16.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.
- [crd]sisa1 game · 1.6% of games in this matchup · Mean recorded OS 44.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.
- [DmE]Gond0r1 game · 1.6% of games in this matchup · Mean recorded OS 30.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.
- [GER]Lord_Zymon1 game · 1.6% of games in this matchup · Mean recorded OS 16.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.
- [WNTR]_Fenris_SC21 game · 1.6% of games in this matchup · Mean recorded OS 24.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.
- _Hawkey_1 game · 1.6% of games in this matchup · Mean recorded OS 60.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.
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 106 recorded opponents.
Geo sea vs Beach sea
2 matched games · 2 distinct opponents · Mean opponent OS 32.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.
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. | 4,117.3 metal | 3,265.9 metal | 100.0%2 paired games |
| Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction. | 5,061.8 metal | 4,137.9 metal | 100.0%2 paired games |
| Energy producedTotal energy produced by this player by this time. | 32,125.8 energy | 37,676.4 energy | 100.0%2 paired games |
| Damage dealtRecorded damage dealt across the match, including fights outside this lane. | 36.8 damage | 0.0 damage | 100.0%2 paired games |
| Damage receivedRecorded damage received across the match, including fights outside this lane. | 0.0 damage | 36.8 damage | 100.0%2 paired games |
| Units producedTotal units produced by this time, including buildings. | 31.5 units | 35.5 units | 100.0%2 paired games |
| All units lostRecorded total units lost, including noncombat losses and buildings. | 3.0 units | 0.5 units | 100.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. | 51.5 metal | 0.0 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. | 0.0 metal | 0.0 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.0 units | 100.0%2 paired games |
- Hummell1 game · 50.0% of games in this matchup · Mean recorded OS 46.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.
- ukuk1 game · 50.0% of games in this matchup · Mean recorded OS 19.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.
Why some selected games have no identified lane:
- No individual lane assigned for this position: 8 games.
- Starting-position records unavailable: 5 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.
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.
Front (suicide)
57.1 / 100
Why this score?Front (second)
52.9 / 100
Why this score?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
More measured games are needed for traits.
Explore this positionTech
More measured games are needed for traits.
Explore this positionPond
More measured games are needed for traits.
Explore this positionFront (suicide)
Rocketeer-heavy by 10:00 63.8%
By 10:00, completed at least 5 Rocketeer 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 63.8% of comparable measured games. Average built in games with data: 22.33 Rocketeer units by 10:00.
Games with measurements for this trait: 75.8%.Opens with Bot Lab 87.1%
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 87.1% 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%.Front (second)
Blitz-heavy by 10:00 70.0%
By 10:00, completed at least 5 Blitz 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 70% of comparable measured games. Average built in games with data: 24.27 Blitz units by 10:00.
Games with measurements for this trait: 83.3%.Opens with Rover 83.3%
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. Rover was the first observed fighting unit start by 5:00 in 83.3% 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%.Geo 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: 103 published games lasting at least five minutes, linked to account 359574. 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: 90.3% 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.