BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 19051

AbyssFalcon

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

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

152026-09-05
to 2026-09-11
432026-09-12
to 2026-09-18
292026-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: 78.8% of selected games.

Selected games: 113 · Games with identified lanes: 89.

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

Front (second) vs Shared central front · shared frontline

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

8 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,910.8 metal3,375.9 metal100.0%8 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,436.0 metal4,235.9 metal100.0%8 paired games
Energy producedTotal energy produced by this player by this time.40,484.3 energy49,021.1 energy100.0%8 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.12,027.6 damage13,025.8 damage100.0%8 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.13,989.5 damage12,563.2 damage100.0%8 paired games
Units producedTotal units produced by this time, including buildings.45.1 units40.2 units100.0%8 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.21.5 units9.0 units25.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.2,368.7 metal1,683.7 metal87.5%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.1,978.4 metal1,660.9 metal87.5%7 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.11.9 units6.1 units87.5%7 paired games
  • 0neTw01 game · 12.5% of games in this matchup · Mean recorded OS 40.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.
  • [JUDGES]kkarinen1 game · 12.5% of games in this matchup · Mean recorded OS 14.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.
  • AcOrP1 game · 12.5% of games in this matchup · Mean recorded OS 25.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.
  • annie_may_tydease1 game · 12.5% of games in this matchup · Mean recorded OS 32.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.
  • DingusMaximus1 game · 12.5% of games in this matchup · Mean recorded OS 19.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.
  • GoldReasons1 game · 12.5% of games in this matchup · Mean recorded OS 29.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.
  • GuiTou1 game · 12.5% of games in this matchup · Mean recorded OS 35.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.
  • Joe30201 game · 12.5% of games in this matchup · Mean recorded OS 17.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.
  • krtf1 game · 12.5% of games in this matchup · Mean recorded OS 44.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.
  • N3CROVicio1 game · 12.5% of games in this matchup · Mean recorded OS 10.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.
  • nenovalexsandr1 game · 12.5% 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.
  • nhs_lover1 game · 12.5% of games in this matchup · Mean recorded OS 31.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.
  • PrivatePershing1 game · 12.5% 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.
  • realisticjo1 game · 12.5% of games in this matchup · Mean recorded OS 33.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.
  • superbadday1 game · 12.5% of games in this matchup · Mean recorded OS 14.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.
  • The_Brawler1 game · 12.5% of games in this matchup · Mean recorded OS 18.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%.

Front (suicide) vs Shared central front · shared frontline

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

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

70 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,485.9 metal3,751.2 metal100.0%70 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.5,026.1 metal4,192.1 metal100.0%70 paired games
Energy producedTotal energy produced by this player by this time.47,722.6 energy47,122.4 energy100.0%70 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.13,971.9 damage12,196.4 damage100.0%70 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.16,904.0 damage11,232.9 damage100.0%70 paired games
Units producedTotal units produced by this time, including buildings.47.2 units43.0 units100.0%70 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.17.1 units15.4 units41.4%29 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.2,742.7 metal1,632.6 metal92.9%65 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.2,347.5 metal1,780.8 metal92.9%65 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.11.3 units7.3 units92.9%65 paired games
  • FrontLiner69er4 games · 5.7% of games in this matchup · Mean recorded OS 31.3Profile owner’s team won 25.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • What_is_Front4 games · 5.7% of games in this matchup · Mean recorded OS 17.3Profile owner’s team won 75.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • CougarKat3 games · 4.3% of games in this matchup · Mean recorded OS 11.4Profile 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.
  • FacelessDude3 games · 4.3% of games in this matchup · Mean recorded OS 27.9Profile 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.
  • Marsdex3 games · 4.3% of games in this matchup · Mean recorded OS 25.6Profile 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.
  • [Blahaj]varunda2 games · 2.9% of games in this matchup · Mean recorded OS 16.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.
  • DontStreamSnipeMeBro2 games · 2.9% of games in this matchup · Mean recorded OS 31.0Profile 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.
  • Failing_Upwards2 games · 2.9% of games in this matchup · Mean recorded OS 32.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.
  • Fakepilot2 games · 2.9% of games in this matchup · Mean recorded OS 34.9Profile 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.
  • Fanatico2 games · 2.9% of games in this matchup · Mean recorded OS 18.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.
  • GazzGrim2 games · 2.9% of games in this matchup · Mean recorded OS 31.2Profile 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.
  • gy0h6y2 games · 2.9% of games in this matchup · Mean recorded OS 30.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.
  • Heuristic_Vigil2 games · 2.9% of games in this matchup · Mean recorded OS 24.3Profile 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.
  • PrivatePershing2 games · 2.9% of games in this matchup · Mean recorded OS 32.6Profile 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.
  • realisticjo2 games · 2.9% of games in this matchup · Mean recorded OS 32.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.
  • Soliloqueur2 games · 2.9% of games in this matchup · Mean recorded OS 41.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.
  • 13litz1 game · 1.4% of games in this matchup · Mean recorded OS 28.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.
  • [AMADO]MyDude1 game · 1.4% of games in this matchup · Mean recorded OS 32.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.
  • [AoW]Vritrasura1 game · 1.4% of games in this matchup · Mean recorded OS 26.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.
  • [BS]Hellzie1 game · 1.4% of games in this matchup · Mean recorded OS 37.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%.

Showing 20 of 117 recorded opponents.

Geo sea vs Beach sea

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

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.4,989.0 metal3,780.0 metal100.0%11 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.6,098.4 metal4,413.4 metal100.0%11 paired games
Energy producedTotal energy produced by this player by this time.65,054.5 energy60,065.3 energy100.0%11 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,808.8 damage1,031.9 damage100.0%11 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,247.2 damage1,821.8 damage100.0%11 paired games
Units producedTotal units produced by this time, including buildings.53.3 units47.1 units100.0%11 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.6.5 units5.8 units90.9%10 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.134.3 metal373.9 metal90.9%10 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.381.1 metal123.9 metal90.9%10 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.3 units2.1 units90.9%10 paired games
  • 50SACINMYSOCIDGAF1 game · 9.1% 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.
  • BasTid1 game · 9.1% of games in this matchup · Mean recorded OS 19.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.
  • Big_Justin1 game · 9.1% 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.
  • frikonja1 game · 9.1% of games in this matchup · Mean recorded OS 26.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.
  • JesterB1 game · 9.1% 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.
  • Niet_Philipp1 game · 9.1% of games in this matchup · Mean recorded OS 14.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.
  • occ1 game · 9.1% 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.
  • PapaJo1 game · 9.1% of games in this matchup · Mean recorded OS 14.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.
  • Quickmercury1 game · 9.1% of games in this matchup · Mean recorded OS 28.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.
  • Shadowisper1 game · 9.1% of games in this matchup · Mean recorded OS 19.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.
  • TTAC1 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: 18 games.
  • Starting-position records unavailable: 6 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.

Front (suicide)

Supreme Isthmus v2.1 · Large teams · 16 players

52.7 / 100

46 scored games · 64.8% coverage.

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

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

Why this score?

Geo tech

Supreme Isthmus v2.1 · Large teams · 16 players

58.1 / 100

9 scored games · 90.0% coverage.

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

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

Why this score?

Pond

Supreme Isthmus v2.1 · Large teams · 16 players

51.2 / 100

5 scored games · 100.0% coverage.

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

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

Why this score?

Geo sea

Supreme Isthmus v2.1 · Large teams · 16 players

56.8 / 100

7 scored games · 70.0% 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, 10:50 UTC.

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

Geo sea

11 selected games

Opens with Crossbow 90.9%

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

Front (suicide)

68 selected games

Thug-heavy by 10:00 66.7%

By 10:00, completed at least 5 Thug 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 66.7% of comparable measured games. Average built in games with data: 28.78 Thug units by 10:00.

Games with measurements for this trait: 57.4%.
Opens with Grunt 91.2%

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

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.

Common first fighting unitFirst T2 constructorUnits received from teammatesBuilds after enemy bombers
About these results

Included: 117 published games lasting at least five minutes, linked to account 19051. 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: 91.5% 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.