BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 100403

SauceDispenser

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

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

392026-09-05
to 2026-09-11
172026-09-12
to 2026-09-18
262026-09-19
to 2026-09-25
172026-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: 50.0% of selected games.

Selected games: 102 · Games with identified lanes: 51.

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

Beach sea vs Geo sea

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

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,563.3 metal3,676.0 metal100.0%7 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,188.6 metal4,064.1 metal100.0%7 paired games
Energy producedTotal energy produced by this player by this time.33,731.1 energy46,056.7 energy100.0%7 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.2,046.2 damage1,910.1 damage100.0%7 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.2,466.5 damage1,886.1 damage100.0%7 paired games
Units producedTotal units produced by this time, including buildings.35.3 units36.6 units100.0%7 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.377.3 metal186.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.272.7 metal280.3 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.2.0 units0.7 units100.0%7 paired games
  • Slump2 games · 28.6% of games in this matchup · Mean recorded OS 36.8Profile 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.
  • Andir1 game · 14.3% of games in this matchup · Mean recorded OS 20.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.
  • Gawd1 game · 14.3% of games in this matchup · Mean recorded OS 11.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.
  • krtf1 game · 14.3% of games in this matchup · Mean recorded OS 42.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.
  • ParadiseLost1 game · 14.3% of games in this matchup · Mean recorded OS 25.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.
  • TheSituation1 game · 14.3% of games in this matchup · Mean recorded OS 46.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

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

28 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,944.2 metal3,554.7 metal100.0%28 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,347.1 metal4,202.1 metal100.0%28 paired games
Energy producedTotal energy produced by this player by this time.43,419.1 energy47,032.0 energy100.0%28 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.12,401.5 damage12,625.7 damage100.0%28 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.12,615.9 damage13,156.9 damage100.0%28 paired games
Units producedTotal units produced by this time, including buildings.46.3 units44.2 units100.0%28 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.10.8 units14.7 units17.9%5 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,089.0 metal1,423.7 metal92.9%26 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,371.4 metal1,057.3 metal92.9%26 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.7.9 units7.3 units92.9%26 paired games
  • ManBearPig_3 games · 10.7% of games in this matchup · Mean recorded OS 38.1Profile 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.
  • Call_Me_Sir2 games · 7.1% of games in this matchup · Mean recorded OS 33.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.
  • Chancho2 games · 7.1% 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.
  • hoze2 games · 7.1% 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.
  • Hummell2 games · 7.1% of games in this matchup · Mean recorded OS 44.7Profile 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.
  • PlatinumBlonde2 games · 7.1% of games in this matchup · Mean recorded OS 56.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.
  • Slump2 games · 7.1% of games in this matchup · Mean recorded OS 38.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.
  • XuunnY2 games · 7.1% of games in this matchup · Mean recorded OS 34.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.
  • AcquiredTaste1 game · 3.6% of games in this matchup · Mean recorded OS 30.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.
  • aikatsu1 game · 3.6% of games in this matchup · Mean recorded OS 37.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.
  • arcsiz1 game · 3.6% 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.
  • BM_akumar61 game · 3.6% of games in this matchup · Mean recorded OS 40.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.
  • Boozha1 game · 3.6% of games in this matchup · Mean recorded OS 31.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.
  • c4commando1 game · 3.6% 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.
  • CentientWaffle1 game · 3.6% of games in this matchup · Mean recorded OS 32.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.
  • cmilly1 game · 3.6% of games in this matchup · Mean recorded OS 16.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.
  • Crimsco1 game · 3.6% 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.
  • DAKILA1 game · 3.6% 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.
  • DAQQ1 game · 3.6% of games in this matchup · Mean recorded OS 15.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.
  • derkarl1 game · 3.6% of games in this matchup · Mean recorded OS 38.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.

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

Front (suicide) vs Shared central front · shared frontline

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

7 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,900.5 metal3,505.0 metal100.0%7 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,429.5 metal4,000.5 metal100.0%7 paired games
Energy producedTotal energy produced by this player by this time.42,944.4 energy43,921.7 energy100.0%7 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.16,195.4 damage13,070.3 damage100.0%7 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.15,087.1 damage16,345.6 damage100.0%7 paired games
Units producedTotal units produced by this time, including buildings.50.7 units44.5 units100.0%7 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.13.3 units22.0 units42.9%3 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,434.7 metal1,666.6 metal85.7%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.1,537.7 metal1,427.5 metal85.7%6 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.10.0 units7.2 units85.7%6 paired games
  • Xzhinn2 games · 28.6% of games in this matchup · Mean recorded OS 50.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.
  • Andir1 game · 14.3% of games in this matchup · Mean recorded OS 20.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.
  • El_Turco1 game · 14.3% of games in this matchup · Mean recorded OS 29.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.
  • goldsmith121 game · 14.3% of games in this matchup · Mean recorded OS 11.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.
  • Hummell1 game · 14.3% of games in this matchup · Mean recorded OS 43.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.
  • Immort1 game · 14.3% of games in this matchup · Mean recorded OS 51.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.
  • iUzername1 game · 14.3% of games in this matchup · Mean recorded OS 28.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.
  • Kcorp1 game · 14.3% of games in this matchup · Mean recorded OS 50.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 · 14.3% of games in this matchup · Mean recorded OS 43.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.
  • RTX1770131 game · 14.3% of games in this matchup · Mean recorded OS 34.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.
  • Un1ucky1 game · 14.3% of games in this matchup · Mean recorded OS 16.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.
  • Vulyer1 game · 14.3% 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.
  • XXMACGAMERXX1 game · 14.3% of games in this matchup · Mean recorded OS 35.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.

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

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

9 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.7,926.9 metal6,607.3 metal100.0%9 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.9,228.1 metal7,294.7 metal100.0%9 paired games
Energy producedTotal energy produced by this player by this time.138,207.7 energy113,479.0 energy100.0%9 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.881.8 damage898.4 damage100.0%9 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.780.3 damage984.9 damage100.0%9 paired games
Units producedTotal units produced by this time, including buildings.67.4 units52.6 units100.0%9 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.12.2 units19.2 units44.4%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.130.6 metal320.2 metal55.6%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.302.0 metal140.6 metal55.6%5 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.1.0 units1.4 units55.6%5 paired games
  • [BS]_Gremlin1 game · 11.1% of games in this matchup · Mean recorded OS 29.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.
  • CentientWaffle1 game · 11.1% 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.
  • Chumpzilla1 game · 11.1% of games in this matchup · Mean recorded OS 13.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.
  • CowFu1 game · 11.1% 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.
  • rooks[vegan]1 game · 11.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.
  • soloszgame1 game · 11.1% of games in this matchup · Mean recorded OS 12.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.
  • Tink3r1 game · 11.1% 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.
  • TK4731 game · 11.1% of games in this matchup · Mean recorded OS 22.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.
  • Vaticineur1 game · 11.1% 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.

Why some selected games have no identified lane:

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

Performance by position

Prepared ranking results, with the same calculation and evidence as the rankings page. Scores are not OS or a share of team victory.

Pond

Supreme Isthmus v2.1 · Large teams · 16 players

52.1 / 100

11 scored games · 61.1% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 55.3 recent vs 51.5 earlier, split at 06 Sep 2026. Approximate change range: -3.9 to 12.1 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Front (second)

Supreme Isthmus v2.1 · Large teams · 16 players

52.2 / 100

21 scored games · 77.8% coverage.

Established results · Updated 02 Oct 2026, 08:39 UTC

Earlier vs recent: No clear change. Recorded game scores 57.9 recent vs 47.7 earlier, split at 09 Sep 2026. Approximate change range: -3.7 to 26.8 points. The comparison uses each period’s opponents and reference players; it does not forecast future play.

Why this score?

Air

Supreme Isthmus v2.1 · Large teams · 16 players

54.3 / 100

9 scored games · 64.3% coverage.

Early results · Updated 02 Oct 2026, 08:39 UTC

Recent comparison: more measured games are needed in both periods.

Why this score?

Tech

Supreme Isthmus v2.1 · Large teams · 16 players

52.9 / 100

9 scored games · 75.0% coverage.

Early results · Updated 02 Oct 2026, 08:39 UTC

Recent comparison: more measured games are needed in both periods.

Why this score?

Beach sea

Supreme Isthmus v2.1 · Large teams · 16 players

47.7 / 100

6 scored games · 85.7% coverage.

Early results · Updated 02 Oct 2026, 08:39 UTC

Recent comparison: more measured games are needed in both periods.

Why this score?

Front (suicide)

Supreme Isthmus v2.1 · Large teams · 16 players

47.2 / 100

6 scored games · 85.7% coverage.

Early results · Updated 02 Oct 2026, 08:39 UTC

Recent comparison: more measured games are needed in both periods.

Why this score?

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, 09:41 UTC.

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

Tech

13 selected games

Opens with Bot Lab 69.2%

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

10 selected games

Opens with Legion Drone Plant 60.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. Legion Drone Plant was the first observed factory start by 5:00 in 60% 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

15 selected games

Buys / receives Advanced Construction Bot 84.6%

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 (13 games with complete data). Finished at receipt in 54%; unfinished in 31% (these can overlap). Gifts are included; payment is not recorded.

Games with measurements for this trait: 86.7%.
Explore this position

Front (second)

23 selected games

Economy-focused at 10:00 66.7%

At 10: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 66.7% of comparable measured games. Matching comparison games available for 80% 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.2%.
Opens with Grunt 69.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. Grunt was the first observed fighting unit start by 5:00 in 69.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

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: 140 published games lasting at least five minutes, linked to account 100403. 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: 93.6% 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, 09:26 UTC; this summary prepared 02 Oct 2026, 09:36 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.