BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 326675

annie_may_tydease

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

Latest recorded OS
31.1
29 Sep 2026 · Large teams · 16 players
Recorded games
99
01 Sep 2026–29 Sep 2026 UTC
Maps played
10
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.

252026-09-05
to 2026-09-11
102026-09-12
to 2026-09-18
392026-09-19
to 2026-09-25
182026-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: 60.9% of selected games.

Selected games: 64 · Games with identified lanes: 39.

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

Front (second) vs Shared central front · shared frontline

1 matched game · 2 distinct opponents · Mean opponent OS 30.7.

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.

1 game 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,789.4 metal4,130.4 metal100.0%1 paired game
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,772.0 metal4,418.8 metal100.0%1 paired game
Energy producedTotal energy produced by this player by this time.58,441.7 energy47,199.1 energy100.0%1 paired game
Damage dealtRecorded damage dealt across the match, including fights outside this lane.5,200.8 damage12,754.6 damage100.0%1 paired game
Damage receivedRecorded damage received across the match, including fights outside this lane.6,620.6 damage10,310.2 damage100.0%1 paired game
Units producedTotal units produced by this time, including buildings.47.0 units52.0 units100.0%1 paired game
All units lostRecorded total units lost, including noncombat losses and buildings.5.0 units11.0 units100.0%1 paired game
Metal lost to enemiesMetal cost of completed units and buildings lost to enemies by this time. Includes commanders; excludes unfinished units and reclaim. Wreckage recovered later is not subtracted.155.0 metal998.5 metal100.0%1 paired game
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.758.0 metal677.5 metal100.0%1 paired game
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.5.0 units9.5 units100.0%1 paired game
  • cmilly1 game · 100.0% of games in this matchup · Mean recorded OS 17.7Profile owner’s team won 0.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • yubiyubi1 game · 100.0% of games in this matchup · Mean recorded OS 43.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.

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

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

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.3,882.8 metal3,853.9 metal100.0%23 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,776.8 metal4,411.1 metal100.0%23 paired games
Energy producedTotal energy produced by this player by this time.50,786.7 energy49,053.9 energy100.0%23 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.14,480.9 damage11,728.7 damage100.0%23 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.15,063.5 damage11,747.5 damage100.0%23 paired games
Units producedTotal units produced by this time, including buildings.45.2 units45.7 units100.0%23 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.15.2 units11.2 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,538.5 metal1,418.4 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,589.3 metal1,145.6 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.13.9 units7.7 units95.7%22 paired games
  • [CC]CupOfCoffee2 games · 8.7% 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.
  • AbyssFalcon2 games · 8.7% of games in this matchup · Mean recorded OS 31.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.
  • death4uandme2 games · 8.7% of games in this matchup · Mean recorded OS 25.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.
  • Lapsa2 games · 8.7% of games in this matchup · Mean recorded OS 14.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.
  • OldSpanker2 games · 8.7% of games in this matchup · Mean recorded OS 50.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.
  • SoClose2 games · 8.7% of games in this matchup · Mean recorded OS 9.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.
  • TheGreenFalcon2 games · 8.7% of games in this matchup · Mean recorded OS 26.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.
  • [Crd]Miriftul1 game · 4.3% of games in this matchup · Mean recorded OS 18.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.
  • [crd]sisa1 game · 4.3% of games in this matchup · Mean recorded OS 43.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.
  • [Grump]_Doni1 game · 4.3% of games in this matchup · Mean recorded OS 50.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.
  • alexandar1 game · 4.3% of games in this matchup · Mean recorded OS 25.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.
  • BigJohnny21 game · 4.3% of games in this matchup · Mean recorded OS 30.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.
  • BigUglyBear1 game · 4.3% 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.
  • Boozha1 game · 4.3% 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.
  • CentientWaffle1 game · 4.3% of games in this matchup · Mean recorded OS 32.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.
  • chivin3d1 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.
  • crashninja1 game · 4.3% of games in this matchup · Mean recorded OS 9.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.
  • CzapX1 game · 4.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.
  • Damsko1 game · 4.3% of games in this matchup · Mean recorded OS 38.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.
  • DontPanic521 game · 4.3% of games in this matchup · Mean recorded OS 8.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.

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

Geo sea vs Beach sea

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

15 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,909.8 metal3,480.9 metal100.0%15 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,467.4 metal4,086.4 metal100.0%15 paired games
Energy producedTotal energy produced by this player by this time.39,582.1 energy35,043.9 energy100.0%15 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,657.3 damage1,757.9 damage100.0%15 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,631.7 damage1,851.3 damage100.0%15 paired games
Units producedTotal units produced by this time, including buildings.35.3 units33.6 units100.0%15 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.8 units3.1 units53.3%8 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.137.2 metal258.4 metal80.0%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.229.8 metal128.0 metal80.0%12 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.3 units0.8 units80.0%12 paired games
  • ChaoticNoob1 game · 6.7% of games in this matchup · Mean recorded OS 34.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.
  • Deathrizzle1 game · 6.7% of games in this matchup · Mean recorded OS 23.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.
  • EpicTyrannus1 game · 6.7% of games in this matchup · Mean recorded OS 44.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.
  • fanboi1 game · 6.7% 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.
  • Geronimofo1 game · 6.7% of games in this matchup · Mean recorded OS 34.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.
  • ISX1 game · 6.7% of games in this matchup · Mean recorded OS 17.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.
  • Kyousuke1 game · 6.7% of games in this matchup · Mean recorded OS 14.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.
  • OffensiveNickname1 game · 6.7% 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.
  • PronooP1 game · 6.7% 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.
  • RG221 game · 6.7% of games in this matchup · Mean recorded OS 30.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.
  • Rysica1 game · 6.7% of games in this matchup · Mean recorded OS 36.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.
  • sagflis3211 game · 6.7% 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.
  • Squidlzzz1 game · 6.7% of games in this matchup · Mean recorded OS 3.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.
  • Swampfeet1 game · 6.7% 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.
  • Zetherite1 game · 6.7% of games in this matchup · Mean recorded OS 27.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.

Why some selected games have no identified lane:

  • No individual lane assigned for this position: 21 games.
  • Starting-position records unavailable: 4 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

53.7 / 100

14 scored games · 60.9% coverage.

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

Earlier vs recent: No clear change. Recorded game scores 51.5 recent vs 61.5 earlier, split at 18 Sep 2026. Approximate change range: -28.5 to 9.9 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

54.6 / 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?

Geo sea

Supreme Isthmus v2.1 · Large teams · 16 players

55.1 / 100

8 scored games · 66.7% 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

51.4 / 100

6 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?

Playstyle at a glance

The same prepared traits shown in the BAR Fight widget. Each position keeps its own history; a trait describes a repeated habit, not a skill rating or the right choice in every game.

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

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

Geo sea

15 selected games

Opens with Pawn 93.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. Pawn was the first observed fighting unit start by 5:00 in 93.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

Front (suicide)

21 selected games

Thug-heavy by 10:00 69.2%

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 69.2% of comparable measured games. Average built in games with data: 29.33 Thug units by 10:00.

Games with measurements for this trait: 61.9%.
Opens with Grunt 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. Grunt 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

Geo tech

11 selected games

Opens with Bot Lab 100.0%

The same first observed factory start by 5:00 in at least 60% of at least 10 measured openings. This does not prove that the build finished. Bot Lab was the first observed factory start by 5:00 in 100% of measured openings. Openings without this build and tied starts of different unit types stay in the percentage. A start need not finish.

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

Ask about this player

Open a prepared question for the most played map, then adjust the map, position, game version or reference rating.

About these results

Included: 99 published games lasting at least five minutes, linked to account 326675. 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.9% 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.