BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 552541

HuntressesofArtemis

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

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

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

Selected games: 93 · Games with identified lanes: 55.

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

Front (second) vs Shared central front · shared frontline

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

30 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,101.1 metal3,831.8 metal100.0%30 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,493.8 metal4,405.9 metal100.0%30 paired games
Energy producedTotal energy produced by this player by this time.52,027.3 energy47,825.1 energy100.0%30 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.10,210.2 damage10,464.9 damage100.0%30 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.8,669.3 damage11,839.7 damage100.0%30 paired games
Units producedTotal units produced by this time, including buildings.51.2 units44.8 units100.0%30 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.7.1 units11.9 units43.3%13 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.586.5 metal992.2 metal80.0%24 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.776.9 metal889.4 metal80.0%24 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.5.0 units6.6 units80.0%24 paired games
  • JesterB2 games · 6.7% of games in this matchup · Mean recorded OS 31.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.
  • Oblivionization2 games · 6.7% of games in this matchup · Mean recorded OS 11.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.
  • PRO_Rerory2 games · 6.7% of games in this matchup · Mean recorded OS 51.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.
  • ReduceReclaimRez2 games · 6.7% 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.
  • SnowCritter2 games · 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.
  • What_is_Front2 games · 6.7% of games in this matchup · Mean recorded OS 15.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.
  • [ASOL]Open4201 game · 3.3% of games in this matchup · Mean recorded OS 18.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.
  • [CRD]BayPalm1 game · 3.3% of games in this matchup · Mean recorded OS 13.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.
  • [Crd]DeAnthony1 game · 3.3% 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.
  • [Crd]Zan51 game · 3.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.
  • _X_1 game · 3.3% of games in this matchup · Mean recorded OS 43.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.
  • aeroplane1 game · 3.3% of games in this matchup · Mean recorded OS 23.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.
  • CentientWaffle1 game · 3.3% of games in this matchup · Mean recorded OS 32.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.
  • ChaoticNoob1 game · 3.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.
  • Cokeado1 game · 3.3% of games in this matchup · Mean recorded OS 40.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.
  • CrashnBern111 game · 3.3% of games in this matchup · Mean recorded OS 21.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.
  • death4uandme1 game · 3.3% of games in this matchup · Mean recorded OS 27.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.
  • derkarl1 game · 3.3% of games in this matchup · Mean recorded OS 39.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.
  • DontStreamSnipeMeBro1 game · 3.3% 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.
  • DOUKNOUKKEM1 game · 3.3% 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.

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

Front (suicide) vs Shared central front · shared frontline

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

25 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,227.9 metal3,808.3 metal100.0%25 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,501.0 metal4,376.9 metal100.0%25 paired games
Energy producedTotal energy produced by this player by this time.53,022.4 energy48,348.7 energy100.0%25 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.13,448.6 damage10,939.8 damage100.0%25 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.11,833.1 damage12,527.2 damage100.0%25 paired games
Units producedTotal units produced by this time, including buildings.54.0 units47.5 units100.0%25 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.11.2 units11.5 units44.0%11 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.736.9 metal1,215.1 metal76.0%19 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,260.8 metal832.0 metal76.0%19 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.4.9 units6.2 units76.0%19 paired games
  • Chancho2 games · 8.0% of games in this matchup · Mean recorded OS 26.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.
  • starbird2 games · 8.0% of games in this matchup · Mean recorded OS 30.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.
  • Xad2 games · 8.0% of games in this matchup · Mean recorded OS 47.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.
  • [Crd]AnotherPug1 game · 4.0% of games in this matchup · Mean recorded OS 21.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.
  • AcquiredTaste1 game · 4.0% of games in this matchup · Mean recorded OS 30.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.
  • AOD_vP1xel1 game · 4.0% of games in this matchup · Mean recorded OS 10.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.
  • Ariys1 game · 4.0% of games in this matchup · Mean recorded OS 20.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.
  • Boozha1 game · 4.0% of games in this matchup · Mean recorded OS 36.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.
  • boysback1 game · 4.0% 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.
  • Buckyo1 game · 4.0% 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.
  • CentientWaffle1 game · 4.0% of games in this matchup · Mean recorded OS 32.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.
  • chironex1 game · 4.0% of games in this matchup · Mean recorded OS 25.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.
  • chromed1 game · 4.0% of games in this matchup · Mean recorded OS 26.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.
  • Copperfield1 game · 4.0% of games in this matchup · Mean recorded OS 14.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.
  • Damsko1 game · 4.0% of games in this matchup · Mean recorded OS 38.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.
  • DoctorPinguins1 game · 4.0% of games in this matchup · Mean recorded OS 38.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.
  • Equis1 game · 4.0% 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.
  • Failing_Upwards1 game · 4.0% of games in this matchup · Mean recorded OS 33.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.
  • Fanatico1 game · 4.0% of games in this matchup · Mean recorded OS 13.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.
  • Flerpz1 game · 4.0% of games in this matchup · Mean recorded OS 31.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.

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.

Why some selected games have no identified lane:

  • Starting layout not verified: 1 game.
  • No individual lane assigned for this position: 33 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 (second)

Supreme Isthmus v2.1 · Large teams · 16 players

57.9 / 100

21 scored games · 80.8% coverage.

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

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

Why this score?

Front (suicide)

Supreme Isthmus v2.1 · Large teams · 16 players

54.1 / 100

13 scored games · 72.2% coverage.

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

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

Why this score?

Anti canyon · P8 / P16

All That Glitters v2.2.3 · Large teams · 16 players

53.1 / 100

25 scored games · 80.6% coverage.

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

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

Why this score?

Pond

Supreme Isthmus v2.1 · Large teams · 16 players

48.7 / 100

11 scored games · 57.9% coverage.

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

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

Why this score?

Carry · P7 / P15

All That Glitters v2.2.3 · Large teams · 16 players

55.5 / 100

10 scored games · 58.8% 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-01–2026-09-30 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.

Pond

16 selected games

Buys / receives Advanced Construction Bot 76.9%

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

Games with measurements for this trait: 81.2%.
Opens with Bot Lab 68.8%

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 68.8% 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)

22 selected games

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

Front (second)

29 selected games

No repeated habit met the trait rules in this position.

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: 156 published games lasting at least five minutes, linked to account 552541. 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: 87.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.