BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 498722

WaterBucket

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

Previously seen as Not_op_WaterBucket

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

222026-09-05
to 2026-09-11
162026-09-12
to 2026-09-18
272026-09-19
to 2026-09-25
102026-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: 33.8% of selected games.

Selected games: 80 · Games with identified lanes: 27.

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

Beach sea vs Geo sea

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

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,333.5 metal3,678.4 metal100.0%2 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,013.3 metal4,593.5 metal100.0%2 paired games
Energy producedTotal energy produced by this player by this time.24,975.4 energy46,374.1 energy100.0%2 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.2,693.9 damage53.4 damage100.0%2 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.53.4 damage2,693.9 damage100.0%2 paired games
Units producedTotal units produced by this time, including buildings.25.5 units40.5 units100.0%2 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.0.0 metal227.5 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.227.5 metal0.0 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.0.0 units1.5 units100.0%2 paired games
  • [Grump]hiirifani1 game · 50.0% 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.
  • AcOrP1 game · 50.0% of games in this matchup · Mean recorded OS 23.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

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

6 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,313.3 metal3,895.3 metal100.0%6 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,057.5 metal4,434.6 metal100.0%6 paired games
Energy producedTotal energy produced by this player by this time.42,799.0 energy49,019.0 energy100.0%6 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.10,460.0 damage9,213.5 damage100.0%6 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.8,812.7 damage10,244.7 damage100.0%6 paired games
Units producedTotal units produced by this time, including buildings.42.8 units46.7 units100.0%6 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.14.5 units9.5 units33.3%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.1,299.2 metal1,042.5 metal83.3%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.1,293.6 metal1,310.2 metal83.3%5 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.7.8 units8.5 units83.3%5 paired games
  • [AoW]Vritrasura1 game · 16.7% of games in this matchup · Mean recorded OS 25.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.
  • [MooDeng]NongJohn1 game · 16.7% of games in this matchup · Mean recorded OS 37.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.
  • boysback1 game · 16.7% 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.
  • Cann1bal1 game · 16.7% of games in this matchup · Mean recorded OS 13.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.
  • cjb2301 game · 16.7% 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.
  • conspirator1 game · 16.7% of games in this matchup · Mean recorded OS 25.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.
  • coolglyph1 game · 16.7% of games in this matchup · Mean recorded OS 26.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.
  • Immort1 game · 16.7% of games in this matchup · Mean recorded OS 51.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.
  • Ragnarryt1 game · 16.7% 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.
  • SnowCritter1 game · 16.7% of games in this matchup · Mean recorded OS 27.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.
  • starbird1 game · 16.7% of games in this matchup · Mean recorded OS 29.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.
  • XuunnY1 game · 16.7% of games in this matchup · Mean recorded OS 33.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%.

Front (suicide) vs Shared central front · shared frontline

3 matched games · 6 distinct opponents · Mean opponent OS 21.6.

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.3,642.8 metal3,780.2 metal100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,306.4 metal4,543.3 metal100.0%3 paired games
Energy producedTotal energy produced by this player by this time.42,556.3 energy47,066.8 energy100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.16,397.1 damage9,770.0 damage100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.11,855.8 damage12,401.7 damage100.0%3 paired games
Units producedTotal units produced by this time, including buildings.42.7 units54.2 units100.0%3 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.20.0 units10.0 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.803.7 metal576.5 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.558.0 metal665.0 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.12.0 units5.2 units100.0%3 paired games
  • Chev41 game · 33.3% of games in this matchup · Mean recorded OS 16.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.
  • IdahoNukeLabs1 game · 33.3% 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.
  • JantDarvus1 game · 33.3% of games in this matchup · Mean recorded OS 26.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.
  • JesterB1 game · 33.3% of games in this matchup · Mean recorded OS 33.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.
  • Morleg1 game · 33.3% of games in this matchup · Mean recorded OS 22.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.
  • Skeletor11 game · 33.3% 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.

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

16 matched games · 16 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.

16 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,527.6 metal3,428.9 metal100.0%16 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,346.9 metal4,174.3 metal100.0%16 paired games
Energy producedTotal energy produced by this player by this time.49,202.7 energy37,562.1 energy100.0%16 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.402.4 damage1,654.0 damage100.0%16 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,579.6 damage545.8 damage100.0%16 paired games
Units producedTotal units produced by this time, including buildings.38.7 units36.2 units100.0%16 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.3.8 units1.5 units37.5%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.143.8 metal99.0 metal81.2%13 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.93.2 metal157.2 metal81.2%13 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.2 units0.6 units81.2%13 paired games
  • 102eskadrila1 game · 6.2% of games in this matchup · Mean recorded OS 22.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.
  • Andir1 game · 6.2% of games in this matchup · Mean recorded OS 19.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.
  • Baby_Bismuth1 game · 6.2% of games in this matchup · Mean recorded OS 17.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.
  • BH829261 game · 6.2% of games in this matchup · Mean recorded OS 22.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.
  • caioac19921 game · 6.2% of games in this matchup · Mean recorded OS 5.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.
  • Endersult1 game · 6.2% of games in this matchup · Mean recorded OS 26.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.
  • gering1 game · 6.2% of games in this matchup · Mean recorded OS 10.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.
  • Godmother131 game · 6.2% of games in this matchup · Mean recorded OS 37.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.
  • halo861 game · 6.2% 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.
  • Handicapping_mySelf1 game · 6.2% of games in this matchup · Mean recorded OS 37.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.
  • ikilldatitanic1 game · 6.2% of games in this matchup · Mean recorded OS 12.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.
  • ITz_HonestAbee1 game · 6.2% of games in this matchup · Mean recorded OS 32.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.
  • NFX_Scurvy1 game · 6.2% 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.
  • SHAhh1 game · 6.2% 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.
  • TimeWaster1 game · 6.2% of games in this matchup · Mean recorded OS 26.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.
  • Xanti_171 game · 6.2% of games in this matchup · Mean recorded OS 6.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.

Why some selected games have no identified lane:

  • Starting layout not verified: 1 game.
  • No individual lane assigned for this position: 51 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:46 UTC.

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

Geo sea

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

Air

21 selected games

Bomber-heavy by 15:00 63.6%

By 15:00, finished more bombers than both the matching group’s average and its 75th percentile (the cutoff for the top quarter). This must happen in at least 60% of at least 10 games with data. Building bombers does not prove a bombing run happened. Above both comparison cutoffs in 63.6% of matching games with data at 15:00. Matching comparison games available for 61.1% 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: 52.4%.
Opens with Valiant 90.5%

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 90.5% 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: 90 published games lasting at least five minutes, linked to account 498722. 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: 82.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.