BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 558937

Remelord

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

Latest recorded OS
13.1
28 Sep 2026 · Large teams · 16 players
Recorded games
114
30 Aug 2026–28 Sep 2026 UTC
Maps played
32
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.

352026-09-05
to 2026-09-11
212026-09-12
to 2026-09-18
232026-09-19
to 2026-09-25
122026-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: 46.3% of selected games.

Selected games: 67 · Games with identified lanes: 31.

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

Beach sea vs Geo sea

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

5 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.2,945.2 metal3,513.0 metal100.0%5 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,724.3 metal4,378.0 metal100.0%5 paired games
Energy producedTotal energy produced by this player by this time.38,634.6 energy44,102.1 energy100.0%5 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.4,224.8 damage1,520.2 damage100.0%5 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,717.6 damage4,257.7 damage100.0%5 paired games
Units producedTotal units produced by this time, including buildings.35.2 units40.2 units100.0%5 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.3.0 units4.5 units40.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.280.0 metal534.0 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.497.8 metal294.6 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.1.6 units1.0 units100.0%5 paired games
  • chironex1 game · 20.0% of games in this matchup · Mean recorded OS 24.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.
  • Disgraceful1 game · 20.0% of games in this matchup · Mean recorded OS 23.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.
  • MajorDMP1 game · 20.0% of games in this matchup · Mean recorded OS 5.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.
  • PEKKAausPlatin1 game · 20.0% of games in this matchup · Mean recorded OS 24.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.
  • superschmitty1 game · 20.0% 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.

Front (second) vs Shared central front · shared frontline

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

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.3,832.2 metal4,678.5 metal100.0%2 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,298.2 metal4,656.8 metal100.0%2 paired games
Energy producedTotal energy produced by this player by this time.34,297.2 energy48,615.7 energy100.0%2 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.5,957.1 damage9,735.9 damage100.0%2 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.6,333.4 damage9,796.3 damage100.0%2 paired games
Units producedTotal units produced by this time, including buildings.35.5 units48.5 units100.0%2 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.10.0 units9.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.716.5 metal852.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.406.0 metal2,885.2 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.5.0 units8.0 units100.0%2 paired games
  • Garchungus1 game · 50.0% of games in this matchup · Mean recorded OS 15.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.
  • ITz_Nobsy211 game · 50.0% of games in this matchup · Mean recorded OS 17.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.
  • Satelite1 game · 50.0% of games in this matchup · Mean recorded OS 25.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.
  • voldemord_1 game · 50.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.

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

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

24 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.2,978.8 metal3,208.2 metal100.0%24 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,589.1 metal3,896.0 metal100.0%24 paired games
Energy producedTotal energy produced by this player by this time.49,599.8 energy40,166.7 energy100.0%24 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.613.5 damage1,344.0 damage100.0%24 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,398.3 damage727.2 damage100.0%24 paired games
Units producedTotal units produced by this time, including buildings.40.8 units34.6 units100.0%24 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.8 units1.6 units50.0%12 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.87.0 metal132.5 metal62.5%15 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.132.5 metal87.0 metal62.5%15 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.3 units0.9 units62.5%15 paired games
  • Agrippas2 games · 8.3% of games in this matchup · Mean recorded OS 17.1Profile 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.
  • Emiralp2 games · 8.3% of games in this matchup · Mean recorded OS 18.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.
  • Bartoes1 game · 4.2% of games in this matchup · Mean recorded OS 6.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.
  • Crimsco1 game · 4.2% of games in this matchup · Mean recorded OS 11.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.
  • Defroot1 game · 4.2% of games in this matchup · Mean recorded OS 9.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.
  • HunyaKitti1 game · 4.2% of games in this matchup · Mean recorded OS 11.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.
  • iAspen1 game · 4.2% of games in this matchup · Mean recorded OS 15.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.
  • Kancho1 game · 4.2% of games in this matchup · Mean recorded OS 11.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.
  • kayag1b11 game · 4.2% of games in this matchup · Mean recorded OS 11.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.
  • Kyousuke1 game · 4.2% 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.
  • merlinarach1 game · 4.2% of games in this matchup · Mean recorded OS 18.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.
  • Nitneuq1 game · 4.2% of games in this matchup · Mean recorded OS 15.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.
  • ORBoom1 game · 4.2% of games in this matchup · Mean recorded OS 8.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.
  • Orrery1 game · 4.2% of games in this matchup · Mean recorded OS 32.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.
  • perc30yabba1 game · 4.2% of games in this matchup · Mean recorded OS 14.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.
  • ridinhigh1 game · 4.2% of games in this matchup · Mean recorded OS 9.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.
  • RoyalSchwabe1 game · 4.2% 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.
  • SturmRabe1 game · 4.2% of games in this matchup · Mean recorded OS 1.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.
  • TLAR1 game · 4.2% of games in this matchup · Mean recorded OS 11.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.
  • twg12345651 game · 4.2% of games in this matchup · Mean recorded OS 5.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.

Showing 20 of 22 recorded opponents.

Why some selected games have no identified lane:

  • Starting layout not verified: 1 game.
  • No individual lane assigned for this position: 32 games.
  • Starting-position records unavailable: 3 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.

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

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

Geo sea

24 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

Pond

13 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

14 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 558937. 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.8% 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.