BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 70197

FireStorm424

A quick view of this player’s published replay history. Choose a map below to explore their play in more detail.

Latest recorded OS
17.4
22 Sep 2026 · Large teams · 16 players
Recorded games
93
31 Aug 2026–22 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.

342026-09-05
to 2026-09-11
222026-09-12
to 2026-09-18
122026-09-19
to 2026-09-25
02026-09-26
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: 39.5% of selected games.

Selected games: 81 · Games with identified lanes: 32.

43 distinct recorded opponents · Mean opponent OS 19.4 (OS available in 100.0% of identified games).

Beach sea vs Geo sea

11 matched games · 11 distinct opponents · Mean opponent OS 15.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.

11 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponentCoverage
Metal producedTotal metal produced by this player by this time.3,526.0 metal3,428.9 metal100.0%11 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,154.5 metal4,003.0 metal100.0%11 paired games
Energy producedTotal energy produced by this player by this time.67,440.5 energy47,825.7 energy100.0%11 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.41.2 damage202.9 damage100.0%11 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.215.8 damage91.3 damage100.0%11 paired games
Units producedTotal units produced by this time, including buildings.60.8 units39.3 units100.0%11 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.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.26.8 metal26.4 metal100.0%11 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.28.8 metal17.6 metal100.0%11 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.0 units0.0 units100.0%11 paired games
  • [Crd]CountScary1 game · 9.1% 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.
  • Beyondler1 game · 9.1% of games in this matchup · Mean recorded OS 6.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.
  • c4commando1 game · 9.1% of games in this matchup · Mean recorded OS 22.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.
  • FrogMilk1 game · 9.1% of games in this matchup · Mean recorded OS 21.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.
  • gomomma1 game · 9.1% of games in this matchup · Mean recorded OS 11.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.
  • lowxy1 game · 9.1% of games in this matchup · Mean recorded OS 6.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.
  • mAxAdrAgoN1 game · 9.1% of games in this matchup · Mean recorded OS 11.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.
  • mr_masterboy1 game · 9.1% of games in this matchup · Mean recorded OS 14.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.
  • Pitacupateu1 game · 9.1% of games in this matchup · Mean recorded OS 35.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.
  • SunnyShortAcres1 game · 9.1% of games in this matchup · Mean recorded OS 7.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.
  • TLAR1 game · 9.1% 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.

Front (second) vs Shared central front · shared frontline

8 matched games · 16 distinct opponents · Mean opponent OS 20.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 →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponents (per player)Coverage
Metal producedTotal metal produced by this player by this time.4,319.0 metal3,740.3 metal100.0%8 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,864.2 metal4,134.9 metal100.0%8 paired games
Energy producedTotal energy produced by this player by this time.50,660.5 energy46,991.3 energy100.0%8 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.7,716.4 damage7,736.3 damage100.0%8 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.7,078.1 damage8,143.6 damage100.0%8 paired games
Units producedTotal units produced by this time, including buildings.50.0 units44.6 units100.0%8 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.5.5 units8.5 units50.0%4 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.575.9 metal1,173.9 metal87.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.662.0 metal1,044.3 metal87.5%7 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.3.9 units6.7 units87.5%7 paired games
  • [Crd]DeAnthony1 game · 12.5% of games in this matchup · Mean recorded OS 18.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.
  • a11fred1 game · 12.5% 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.
  • clayton761 game · 12.5% of games in this matchup · Mean recorded OS 9.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.
  • Dampish1 game · 12.5% 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.
  • DeathTeaser1 game · 12.5% 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.
  • Dyingsolarsystem1 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
  • HKHammer1 game · 12.5% 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.
  • ILIKE_2_ECO1 game · 12.5% of games in this matchup · Mean recorded OS 36.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.
  • Kanedias1 game · 12.5% 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.
  • Kjerl1 game · 12.5% of games in this matchup · Mean recorded OS 20.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.
  • Node_271 game · 12.5% of games in this matchup · Mean recorded OS 19.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.
  • ohlaracorp1 game · 12.5% 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.
  • peepeedoodoo1 game · 12.5% of games in this matchup · Mean recorded OS 14.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.
  • poonnc1 game · 12.5% of games in this matchup · Mean recorded OS 7.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.
  • realisticjo1 game · 12.5% of games in this matchup · Mean recorded OS 33.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.
  • StanleyJJ1 game · 12.5% of games in this matchup · Mean recorded OS 18.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.

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

5 matched games · 10 distinct opponents · Mean opponent OS 23.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.

5 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponents (per player)Coverage
Metal producedTotal metal produced by this player by this time.4,233.9 metal3,892.1 metal100.0%5 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,910.6 metal4,430.0 metal100.0%5 paired games
Energy producedTotal energy produced by this player by this time.55,952.1 energy49,630.7 energy100.0%5 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.9,602.1 damage8,904.7 damage100.0%5 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.8,734.0 damage9,629.9 damage100.0%5 paired games
Units producedTotal units produced by this time, including buildings.48.2 units42.4 units100.0%5 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.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,033.0 metal1,392.1 metal100.0%5 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.2,028.4 metal726.3 metal100.0%5 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.7.0 units6.0 units100.0%5 paired games
  • [Crd]DeAnthony1 game · 20.0% of games in this matchup · Mean recorded OS 18.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.
  • [FCRD]GlazedByAfussy1 game · 20.0% of games in this matchup · Mean recorded OS 33.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.
  • AllINoRNOTHING1 game · 20.0% of games in this matchup · Mean recorded OS 19.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.
  • Ampel1 game · 20.0% of games in this matchup · Mean recorded OS 10.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.
  • Atrigna1 game · 20.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.
  • ChaoticNoob1 game · 20.0% of games in this matchup · Mean recorded OS 33.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.
  • Etherift1 game · 20.0% of games in this matchup · Mean recorded OS 34.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.
  • ImpAct13371 game · 20.0% 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.
  • JBH1 game · 20.0% of games in this matchup · Mean recorded OS 16.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.
  • TheBossMoose1 game · 20.0% of games in this matchup · Mean recorded OS 22.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

8 matched games · 8 distinct opponents · Mean opponent OS 22.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.

8 games reached 5:00.

Swipe sideways to compare both sides →

Average per game by 5:00
MeasurementProfile ownerStarting-lane opponentCoverage
Metal producedTotal metal produced by this player by this time.3,877.3 metal3,834.8 metal100.0%8 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,761.9 metal4,092.2 metal100.0%8 paired games
Energy producedTotal energy produced by this player by this time.59,349.2 energy37,084.6 energy100.0%8 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.741.1 damage1,674.3 damage100.0%8 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,965.1 damage1,161.5 damage100.0%8 paired games
Units producedTotal units produced by this time, including buildings.47.4 units33.8 units100.0%8 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.Not recordedNot recorded0.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.331.0 metal169.1 metal100.0%8 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.136.2 metal343.5 metal100.0%8 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.5 units0.6 units100.0%8 paired games
  • Blover1 game · 12.5% of games in this matchup · Mean recorded OS 39.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.
  • c4commando1 game · 12.5% of games in this matchup · Mean recorded OS 22.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.
  • Dahaki1 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.
  • Domdar1 game · 12.5% of games in this matchup · Mean recorded OS 11.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.
  • Hard2kill1 game · 12.5% of games in this matchup · Mean recorded OS 17.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.
  • Imminent1 game · 12.5% of games in this matchup · Mean recorded OS 6.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.
  • kaippeler1 game · 12.5% 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.
  • Poseidon91 game · 12.5% of games in this matchup · Mean recorded OS 36.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.

Why some selected games have no identified lane:

  • No individual lane assigned for this position: 48 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.

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.

Trait period: 2026-09-03–2026-10-02 UTC · Supreme Isthmus v2.1 · human 8v8 · mirrored starts combined. Checked 02 Oct 2026, 10:42 UTC.

Tech

11 selected games

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%.
Explore this position

Geo tech

13 selected games

Opens with Bot Lab 84.6%

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 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%.
Explore this position

Beach sea

12 selected games

Seeker-heavy by 10:00 81.8%

By 10:00, completed at least 5 Seeker 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 81.8% of comparable measured games. Average built in games with data: 24.09 Seeker units by 10:00.

Games with measurements for this trait: 91.7%.
Economy-focused at 5:00 75.0%

At 5:00, economy’s share of completed build value is above both the matching group’s average and its 75th percentile (top-quarter cutoff). The fighting-unit share is below both its average and its 25th percentile (bottom-quarter cutoff). Both must happen in at least 60% of at least 10 games with data. This shows building priorities; it does not prove unsafe greed or poor play. This investment pattern appears in 75% of comparable measured games. Matching comparison games available for 100% of this player’s games with data. Each other player counts equally within a group with the same settings and game version. Results from those groups are combined to match this player’s mix of games.

Games with measurements for this trait: 100.0%.
Opens with Crossbow 66.7%

The 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. Crossbow was the first observed fighting unit start by 5:00 in 66.7% 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%.
Explore this position

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: 93 published games lasting at least five minutes, linked to account 70197. 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.5% 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.