BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 221770

[Crd]Glizzy

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

Latest recorded OS
20.0
28 Sep 2026 · Large teams · 16 players
Recorded games
102
31 Aug 2026–28 Sep 2026 UTC
Maps played
15
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.

112026-09-05
to 2026-09-11
182026-09-12
to 2026-09-18
242026-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: 66.7% of selected games.

Selected games: 48 · Games with identified lanes: 32.

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

Beach sea vs Geo sea

1 matched game · 1 distinct opponent · Mean opponent OS 23.9.

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.

1 game 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,019.3 metal4,023.9 metal100.0%1 paired game
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,785.8 metal5,032.2 metal100.0%1 paired game
Energy producedTotal energy produced by this player by this time.38,682.2 energy60,267.8 energy100.0%1 paired game
Damage dealtRecorded damage dealt across the match, including fights outside this lane.4,080.0 damage2,730.0 damage100.0%1 paired game
Damage receivedRecorded damage received across the match, including fights outside this lane.2,460.1 damage4,358.7 damage100.0%1 paired game
Units producedTotal units produced by this time, including buildings.30.0 units42.0 units100.0%1 paired game
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.500.0 metal130.0 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.130.0 metal500.0 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 units0.0 units100.0%1 paired game
  • Dahaki1 game · 100.0% 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.

Front (second) vs Shared central front · shared frontline

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

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

13 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,668.4 metal3,840.6 metal100.0%13 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,879.9 metal4,538.3 metal100.0%13 paired games
Energy producedTotal energy produced by this player by this time.41,889.6 energy48,812.1 energy100.0%13 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.9,283.7 damage10,977.4 damage100.0%13 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.8,335.3 damage13,634.2 damage100.0%13 paired games
Units producedTotal units produced by this time, including buildings.36.8 units44.3 units100.0%13 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.12.0 units13.5 units38.5%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.703.7 metal1,377.0 metal92.3%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.1,123.3 metal1,090.4 metal92.3%12 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.6.6 units7.3 units92.3%12 paired games
  • XXMACGAMERXX3 games · 23.1% of games in this matchup · Mean recorded OS 33.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.
  • realisticjo2 games · 15.4% of games in this matchup · Mean recorded OS 32.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.
  • [Fx]Doo1 game · 7.7% of games in this matchup · Mean recorded OS 35.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.
  • Alasthor1 game · 7.7% of games in this matchup · Mean recorded OS 9.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.
  • br_aige1 game · 7.7% of games in this matchup · Mean recorded OS 20.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.
  • braindump1 game · 7.7% of games in this matchup · Mean recorded OS 17.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.
  • EAW2X1 game · 7.7% of games in this matchup · Mean recorded OS 9.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.
  • eelander91 game · 7.7% of games in this matchup · Mean recorded OS 11.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.
  • EvilWasp1 game · 7.7% of games in this matchup · Mean recorded OS 23.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.
  • heihallo1 game · 7.7% of games in this matchup · Mean recorded OS 28.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.
  • Heuristic_Vigil1 game · 7.7% of games in this matchup · Mean recorded OS 23.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.
  • HKHammer1 game · 7.7% of games in this matchup · Mean recorded OS 20.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.
  • Hunfore1 game · 7.7% of games in this matchup · Mean recorded OS 31.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.
  • mlem861 game · 7.7% 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.
  • Pacha1 game · 7.7% 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.
  • Sk41 game · 7.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.
  • TimeArtificer1 game · 7.7% of games in this matchup · Mean recorded OS 21.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.
  • TrapCaT1 game · 7.7% of games in this matchup · Mean recorded OS 42.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.
  • Tregan1 game · 7.7% 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.
  • waine1 game · 7.7% of games in this matchup · Mean recorded OS 31.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.

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

Front (suicide) vs Shared central front · shared frontline

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

18 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,515.2 metal3,681.9 metal100.0%18 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,044.9 metal4,084.6 metal100.0%18 paired games
Energy producedTotal energy produced by this player by this time.41,155.8 energy47,157.6 energy100.0%18 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.11,971.9 damage8,563.8 damage100.0%18 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.10,857.0 damage9,263.4 damage100.0%18 paired games
Units producedTotal units produced by this time, including buildings.30.6 units43.0 units100.0%18 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.7.7 units10.1 units50.0%9 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,499.3 metal1,352.1 metal77.8%14 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,384.9 metal1,172.9 metal77.8%14 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.3.0 units6.1 units77.8%14 paired games
  • A_Lias2 games · 11.1% 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.
  • Clappavelli2 games · 11.1% of games in this matchup · Mean recorded OS 20.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.
  • [AMADO]Pacha1 game · 5.6% of games in this matchup · Mean recorded OS 24.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.
  • [Crd]Acquati1 game · 5.6% 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.
  • [Crd]Stinky0161 game · 5.6% of games in this matchup · Mean recorded OS 13.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.
  • [DmE]Launch_rat1 game · 5.6% 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.
  • [JUDGES]JuDgEpowr1 game · 5.6% of games in this matchup · Mean recorded OS 18.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.
  • [JUDGES]Shrapnel1 game · 5.6% 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.
  • AbyssWatcher7771 game · 5.6% of games in this matchup · Mean recorded OS 23.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.
  • AcOrP1 game · 5.6% of games in this matchup · Mean recorded OS 24.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.
  • Ampster161 game · 5.6% of games in this matchup · Mean recorded OS 0.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.
  • br_aige1 game · 5.6% of games in this matchup · Mean recorded OS 20.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.
  • Cal12211 game · 5.6% of games in this matchup · Mean recorded OS 13.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.
  • catlordy1 game · 5.6% of games in this matchup · Mean recorded OS 29.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.
  • Coordinate1 game · 5.6% of games in this matchup · Mean recorded OS 18.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.
  • Endersult1 game · 5.6% 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.
  • FrogMilk1 game · 5.6% of games in this matchup · Mean recorded OS 21.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.
  • GrN11 game · 5.6% 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.
  • GropingSasquatch1 game · 5.6% of games in this matchup · Mean recorded OS 23.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.
  • Heuristic_Vigil1 game · 5.6% of games in this matchup · Mean recorded OS 23.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.

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

Why some selected games have no identified lane:

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

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:51 UTC.

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

Front (suicide)

17 selected games

Opens with Centurion 82.4%

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

12 selected games

Opens with Grunt 66.7%

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 66.7% 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: 102 published games lasting at least five minutes, linked to account 221770. 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.1% 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:41 UTC; this summary prepared 02 Oct 2026, 10:51 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.