BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 543782

[Crd]Noodles

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

Latest recorded OS
28.2
30 Sep 2026 · Large teams · 16 players
Recorded games
79
30 Aug 2026–30 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.

122026-09-05
to 2026-09-11
92026-09-12
to 2026-09-18
292026-09-19
to 2026-09-25
222026-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: 62.7% of selected games.

Selected games: 75 · Games with identified lanes: 47.

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

Beach sea vs Geo sea

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

14 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,721.6 metal3,752.4 metal100.0%14 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,504.0 metal4,486.8 metal100.0%14 paired games
Energy producedTotal energy produced by this player by this time.38,965.1 energy50,767.0 energy100.0%14 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,449.0 damage1,229.2 damage100.0%14 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,548.4 damage1,457.1 damage100.0%14 paired games
Units producedTotal units produced by this time, including buildings.35.9 units42.3 units100.0%14 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.1.7 units3.0 units42.9%6 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.220.2 metal191.5 metal85.7%12 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.193.5 metal160.5 metal85.7%12 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.4 units0.9 units85.7%12 paired games
  • JesterB2 games · 14.3% of games in this matchup · Mean recorded OS 33.5Profile 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.
  • Svinpals2 games · 14.3% of games in this matchup · Mean recorded OS 21.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.
  • AcquiredTaste1 game · 7.1% of games in this matchup · Mean recorded OS 31.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.
  • ANR_Bobba1 game · 7.1% 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.
  • DillWithAWill[y]1 game · 7.1% of games in this matchup · Mean recorded OS 11.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.
  • Gloomy_Plume1 game · 7.1% of games in this matchup · Mean recorded OS 26.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.
  • IM4U2NV1 game · 7.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.
  • JantDarvus1 game · 7.1% of games in this matchup · Mean recorded OS 25.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.
  • Kittensallthewaydown1 game · 7.1% of games in this matchup · Mean recorded OS 20.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.
  • korvin19681 game · 7.1% of games in this matchup · Mean recorded OS 15.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.
  • seryozha1 game · 7.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.
  • Skuldeth1 game · 7.1% of games in this matchup · Mean recorded OS 15.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.

Front (second) vs Shared central front · shared frontline

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

23 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,230.1 metal3,652.5 metal100.0%23 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,435.1 metal4,156.8 metal100.0%23 paired games
Energy producedTotal energy produced by this player by this time.46,856.8 energy45,927.4 energy100.0%23 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.12,503.4 damage11,369.6 damage100.0%23 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.10,811.3 damage12,370.5 damage100.0%23 paired games
Units producedTotal units produced by this time, including buildings.40.0 units45.3 units100.0%23 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.7.2 units14.0 units26.1%6 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,171.3 metal1,473.7 metal95.7%22 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,069.3 metal1,443.7 metal95.7%22 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.8.5 units7.8 units95.7%22 paired games
  • derkarl3 games · 13.0% of games in this matchup · Mean recorded OS 40.0Profile 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.
  • Bsn127782 games · 8.7% of games in this matchup · Mean recorded OS 23.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.
  • CentientWaffle2 games · 8.7% 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.
  • GuiTou2 games · 8.7% of games in this matchup · Mean recorded OS 35.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.
  • XxfuryxX2 games · 8.7% of games in this matchup · Mean recorded OS 24.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.
  • 1LastGameAndSleep1 game · 4.3% 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.
  • 7ead21 game · 4.3% 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.
  • [BS]Hellzie1 game · 4.3% of games in this matchup · Mean recorded OS 39.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.
  • _Astartes_1 game · 4.3% of games in this matchup · Mean recorded OS 13.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.
  • _Hawkey_1 game · 4.3% of games in this matchup · Mean recorded OS 59.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.
  • _nullious_1 game · 4.3% of games in this matchup · Mean recorded OS 27.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.
  • AcquiredTaste1 game · 4.3% of games in this matchup · Mean recorded OS 28.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.
  • Atlasfailed1 game · 4.3% of games in this matchup · Mean recorded OS 36.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.
  • BANBO1 game · 4.3% 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.
  • Beenami1 game · 4.3% of games in this matchup · Mean recorded OS 29.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.
  • CamioGX1 game · 4.3% of games in this matchup · Mean recorded OS 13.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.
  • danecraze1 game · 4.3% of games in this matchup · Mean recorded OS 13.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.
  • Demi9001 game · 4.3% 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.
  • Drakoan1 game · 4.3% of games in this matchup · Mean recorded OS 27.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.
  • Dudeney1 game · 4.3% of games in this matchup · Mean recorded OS 24.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.

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 40 recorded opponents.

Front (suicide) vs Shared central front · shared frontline

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

3 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,038.4 metal3,836.5 metal100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,495.4 metal4,432.0 metal100.0%3 paired games
Energy producedTotal energy produced by this player by this time.43,276.7 energy50,657.0 energy100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.14,200.1 damage9,706.1 damage100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.12,033.0 damage13,638.7 damage100.0%3 paired games
Units producedTotal units produced by this time, including buildings.39.3 units48.5 units100.0%3 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.12.0 units9.5 units33.3%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,899.0 metal968.7 metal100.0%3 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,389.3 metal1,147.7 metal100.0%3 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.5.7 units7.2 units100.0%3 paired games
  • CornyMuesli1 game · 33.3% of games in this matchup · Mean recorded OS 26.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.
  • Hunfore1 game · 33.3% of games in this matchup · Mean recorded OS 33.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.
  • mikimil1 game · 33.3% of games in this matchup · Mean recorded OS 23.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.
  • SoClose1 game · 33.3% of games in this matchup · Mean recorded OS 10.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.
  • TopDog1 game · 33.3% of games in this matchup · Mean recorded OS 30.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.
  • WobblyCommander1 game · 33.3% of games in this matchup · Mean recorded OS 12.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.

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

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

7 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,705.4 metal3,495.0 metal100.0%7 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,697.6 metal4,033.7 metal100.0%7 paired games
Energy producedTotal energy produced by this player by this time.50,129.6 energy35,707.7 energy100.0%7 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.810.4 damage423.9 damage100.0%7 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.557.2 damage596.2 damage100.0%7 paired games
Units producedTotal units produced by this time, including buildings.40.9 units33.4 units100.0%7 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.3.2 units1.2 units57.1%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.80.6 metal115.9 metal100.0%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.152.9 metal87.4 metal100.0%7 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.4 units0.9 units100.0%7 paired games
  • [IF]Yoshii1 game · 14.3% 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.
  • _X_1 game · 14.3% of games in this matchup · Mean recorded OS 43.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.
  • KingAztec0101 game · 14.3% of games in this matchup · Mean recorded OS 28.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.
  • PsDaemonAir1 game · 14.3% of games in this matchup · Mean recorded OS 19.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.
  • RTS_MaJoR1 game · 14.3% of games in this matchup · Mean recorded OS 28.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.
  • SleepingBoy1 game · 14.3% of games in this matchup · Mean recorded OS 15.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.
  • Warmoob1 game · 14.3% of games in this matchup · Mean recorded OS 25.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.

Why some selected games have no identified lane:

  • No individual lane assigned for this position: 27 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, 10:44 UTC.

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

Front (second)

23 selected games

Opens with Rover 100.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. Rover was the first observed fighting unit 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

Beach sea

14 selected games

Opens with Riptide 64.3%

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. Riptide was the first observed fighting unit start by 5:00 in 64.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%.
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: 79 published games lasting at least five minutes, linked to account 543782. 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: 96.2% 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.