BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 587361

Aydan

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

Latest recorded OS
26.6
24 Sep 2026 · Large teams · 16 players
Recorded games
114
30 Aug 2026–25 Sep 2026 UTC
Maps played
5
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
422026-09-12
to 2026-09-18
362026-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: 16.2% of selected games.

Selected games: 99 · Games with identified lanes: 16.

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

Beach sea vs Geo sea

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

2 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,440.1 metal3,593.7 metal100.0%2 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,057.3 metal4,098.4 metal100.0%2 paired games
Energy producedTotal energy produced by this player by this time.34,829.6 energy46,618.3 energy100.0%2 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.9,296.0 damage2,763.6 damage100.0%2 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.2,348.1 damage11,041.2 damage100.0%2 paired games
Units producedTotal units produced by this time, including buildings.26.5 units37.0 units100.0%2 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.1.0 units10.0 units50.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.412.5 metal730.0 metal100.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.556.0 metal387.5 metal100.0%2 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.2.5 units1.5 units100.0%2 paired games
  • El_Turco1 game · 50.0% of games in this matchup · Mean recorded OS 31.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.
  • OlFrosty1 game · 50.0% of games in this matchup · Mean recorded OS 24.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.

Front (second) vs Shared central front · shared frontline

1 matched game · 2 distinct opponents · Mean opponent OS 42.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.

1 game 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.3,577.4 metal4,076.9 metal100.0%1 paired game
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,573.1 metal4,723.9 metal100.0%1 paired game
Energy producedTotal energy produced by this player by this time.43,235.8 energy54,977.2 energy100.0%1 paired game
Damage dealtRecorded damage dealt across the match, including fights outside this lane.18,060.4 damage11,334.5 damage100.0%1 paired game
Damage receivedRecorded damage received across the match, including fights outside this lane.12,448.2 damage10,209.0 damage100.0%1 paired game
Units producedTotal units produced by this time, including buildings.34.0 units45.0 units100.0%1 paired game
All units lostRecorded total units lost, including noncombat losses and buildings.8.0 units1.5 units100.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.643.0 metal152.5 metal100.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.220.0 metal999.5 metal100.0%1 paired game
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.3.0 units0.0 units100.0%1 paired game
  • Boozha1 game · 100.0% of games in this matchup · Mean recorded OS 36.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.
  • Derpiederp1 game · 100.0% of games in this matchup · Mean recorded OS 48.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

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

For shared Front, the opponent average is per opposing player in each game, and both opposing players must have records.

2 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,571.3 metal3,905.6 metal100.0%2 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,582.2 metal4,359.6 metal100.0%2 paired games
Energy producedTotal energy produced by this player by this time.45,054.5 energy48,060.0 energy100.0%2 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.9,271.6 damage6,565.1 damage100.0%2 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.7,903.2 damage6,486.2 damage100.0%2 paired games
Units producedTotal units produced by this time, including buildings.42.0 units37.8 units100.0%2 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.0 units5.0 units50.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,083.0 metal1,196.5 metal50.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,453.0 metal1,136.0 metal50.0%1 paired game
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.9.0 units6.0 units50.0%1 paired game
  • [TTV]Cookie1 game · 50.0% 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.
  • [UoB]m1ll3nium1 game · 50.0% of games in this matchup · Mean recorded OS 28.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.
  • longsongzlc1 game · 50.0% of games in this matchup · Mean recorded OS 9.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.
  • LOOKSAUS1 game · 50.0% 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.

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

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

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,800.6 metal3,218.0 metal100.0%11 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,446.4 metal3,974.8 metal100.0%11 paired games
Energy producedTotal energy produced by this player by this time.48,723.1 energy35,503.4 energy100.0%11 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.932.1 damage1,519.8 damage100.0%11 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.997.4 damage1,258.8 damage100.0%11 paired games
Units producedTotal units produced by this time, including buildings.36.2 units34.0 units100.0%11 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.3.2 units1.8 units81.8%9 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.102.3 metal257.0 metal54.5%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.200.3 metal167.5 metal54.5%6 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.2 units2.2 units54.5%6 paired games
  • cmilly1 game · 9.1% of games in this matchup · Mean recorded OS 16.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.
  • D4rkF0restTheory1 game · 9.1% of games in this matchup · Mean recorded OS 21.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.
  • Gyrimar1 game · 9.1% of games in this matchup · Mean recorded OS 24.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.
  • JesterB1 game · 9.1% of games in this matchup · Mean recorded OS 32.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.
  • krtf1 game · 9.1% of games in this matchup · Mean recorded OS 41.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.
  • Lexosis1 game · 9.1% of games in this matchup · Mean recorded OS 35.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.
  • Marinebirch7231 game · 9.1% of games in this matchup · Mean recorded OS 7.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.
  • theking3911 game · 9.1% of games in this matchup · Mean recorded OS 24.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.
  • Thuryn1 game · 9.1% 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.
  • zerodawn1201 game · 9.1% of games in this matchup · Mean recorded OS 9.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.
  • Zveroboi1 game · 9.1% of games in this matchup · Mean recorded OS 15.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.

Why some selected games have no identified lane:

  • No individual lane assigned for this position: 82 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-02–2026-10-01 UTC · Supreme Isthmus v2.1 · human 8v8 · mirrored starts combined. Checked 02 Oct 2026, 11:49 UTC.

These traits are awaiting a refresh. They describe the period printed above.

Geo sea

12 selected games

Opens with Bot Lab 66.7%

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 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

Air

30 selected games

Opens with Valiant 80.0%

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. Valiant was the first observed fighting unit start by 5:00 in 80% 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

Pond

37 selected games

Buys / receives Advanced Construction Bot 85.3%

Common teammate unit transfers while playing Pond. These may include gifts; payment is not recorded. Advanced Construction Bot received from a teammate by 10:00 in 85% of observed Pond games (34 games with complete data). Finished at receipt in 62%; unfinished in 24% (these can overlap). Gifts are included; payment is not recorded.

Games with measurements for this trait: 91.9%.
Blitz-heavy by 10:00 82.1%

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 82.1% of comparable measured games. Average built in games with data: 12.03 Blitz units by 10:00.

Games with measurements for this trait: 75.7%.
Opens with Blitz 67.6%

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. Blitz was the first observed fighting unit start by 5:00 in 67.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

Geo tech

12 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

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: 114 published games lasting at least five minutes, linked to account 587361. 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: 86.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: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.