BAR FIGHTBeyond All Reason · replay statistics

Player profile · Account 501027

Hannodins

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

Latest recorded OS
37.1
29 Sep 2026 · Large teams · 16 players
Recorded games
103
31 Aug 2026–29 Sep 2026 UTC
Maps played
27
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.

212026-09-05
to 2026-09-11
202026-09-12
to 2026-09-18
182026-09-19
to 2026-09-25
192026-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: 73.5% of selected games.

Selected games: 68 · Games with identified lanes: 50.

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

Beach sea vs Geo sea

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

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.3,393.9 metal3,656.4 metal100.0%11 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,124.1 metal4,321.8 metal100.0%11 paired games
Energy producedTotal energy produced by this player by this time.34,937.2 energy44,740.2 energy100.0%11 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.3,646.9 damage999.2 damage100.0%11 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,298.9 damage2,281.3 damage100.0%11 paired games
Units producedTotal units produced by this time, including buildings.30.7 units40.1 units100.0%11 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.3.0 units5.0 units9.1%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.116.0 metal191.8 metal100.0%11 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.366.0 metal123.1 metal100.0%11 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.0.7 units0.7 units100.0%11 paired games
  • [BS]Nampukk1 game · 9.1% of games in this matchup · Mean recorded OS 29.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.
  • [GER]Lord_Zymon1 game · 9.1% of games in this matchup · Mean recorded OS 19.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.
  • _X_1 game · 9.1% 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.
  • AcquiredTaste1 game · 9.1% of games in this matchup · Mean recorded OS 28.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.
  • Alphacure1 game · 9.1% of games in this matchup · Mean recorded OS 35.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.
  • arcsiz1 game · 9.1% of games in this matchup · Mean recorded OS 34.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.
  • Bestoloch1 game · 9.1% 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.
  • eulis4n1 game · 9.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.
  • MrCoolPotato1 game · 9.1% of games in this matchup · Mean recorded OS 41.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.
  • Obliteratus1 game · 9.1% of games in this matchup · Mean recorded OS 12.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.
  • Zeker_niet_Philipp1 game · 9.1% of games in this matchup · Mean recorded OS 36.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.

Front (second) vs Shared central front · shared frontline

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

19 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,927.2 metal3,606.2 metal100.0%19 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,800.8 metal4,191.8 metal100.0%19 paired games
Energy producedTotal energy produced by this player by this time.55,350.1 energy47,550.2 energy100.0%19 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.6,337.3 damage8,746.0 damage100.0%19 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.5,991.3 damage10,310.6 damage100.0%19 paired games
Units producedTotal units produced by this time, including buildings.53.0 units45.3 units100.0%19 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.10.0 units10.8 units21.1%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.802.6 metal1,166.6 metal94.7%18 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.496.6 metal1,077.0 metal94.7%18 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.5.8 units6.6 units94.7%18 paired games
  • HALF_DALLAH_HABIT3 games · 15.8% of games in this matchup · Mean recorded OS 30.7Profile owner’s team won 66.7% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Vaticineur2 games · 10.5% of games in this matchup · Mean recorded OS 31.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.
  • 3nZ1 game · 5.3% of games in this matchup · Mean recorded OS 12.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.
  • [BS]RohNiN1 game · 5.3% of games in this matchup · Mean recorded OS 38.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.
  • AcquiredTaste1 game · 5.3% of games in this matchup · Mean recorded OS 30.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.
  • BasTid1 game · 5.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.
  • derkarl1 game · 5.3% of games in this matchup · Mean recorded OS 34.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.
  • Erilium1 game · 5.3% of games in this matchup · Mean recorded OS 45.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.
  • GncYz891 game · 5.3% of games in this matchup · Mean recorded OS 16.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.
  • Godmother131 game · 5.3% of games in this matchup · Mean recorded OS 37.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.
  • ieNemo1 game · 5.3% 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.
  • ILIKE_2_ECO1 game · 5.3% of games in this matchup · Mean recorded OS 35.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.
  • ivan22101 game · 5.3% of games in this matchup · Mean recorded OS 6.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.
  • JesterB1 game · 5.3% of games in this matchup · Mean recorded OS 32.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.
  • Kawaii[Ric]1 game · 5.3% of games in this matchup · Mean recorded OS 13.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.
  • kenchi1 game · 5.3% of games in this matchup · Mean recorded OS 33.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.
  • ManBearPig_1 game · 5.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.
  • matje2o1 game · 5.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.
  • Messerschmitt1 game · 5.3% of games in this matchup · Mean recorded OS 12.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.
  • NastyNoob1 game · 5.3% of games in this matchup · Mean recorded OS 16.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.

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

Front (suicide) vs Shared central front · shared frontline

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

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.4,034.9 metal3,794.7 metal100.0%8 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,450.3 metal4,305.1 metal100.0%8 paired games
Energy producedTotal energy produced by this player by this time.47,124.5 energy48,247.2 energy100.0%8 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.11,431.0 damage8,307.0 damage100.0%8 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.11,223.2 damage10,069.2 damage100.0%8 paired games
Units producedTotal units produced by this time, including buildings.48.0 units43.8 units100.0%8 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.10.5 units11.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.1,680.8 metal1,236.6 metal62.5%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.1,682.0 metal1,147.3 metal62.5%5 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.6.8 units7.2 units62.5%5 paired games
  • MokkaZaZa2 games · 25.0% of games in this matchup · Mean recorded OS 13.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.
  • ChaoticMlem1 game · 12.5% of games in this matchup · Mean recorded OS 8.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.
  • ChaoticNoob1 game · 12.5% of games in this matchup · Mean recorded OS 33.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.
  • Comas1 game · 12.5% of games in this matchup · Mean recorded OS 14.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.
  • derkarl1 game · 12.5% 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.
  • dmdm1 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.
  • Dorsch1231 game · 12.5% of games in this matchup · Mean recorded OS 31.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.
  • HuntressesofArtemis1 game · 12.5% of games in this matchup · Mean recorded OS 36.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.
  • ITz_Nobsy211 game · 12.5% of games in this matchup · Mean recorded OS 17.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.
  • Jonjo_131 game · 12.5% of games in this matchup · Mean recorded OS 28.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.
  • JumboJimbo1 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
  • Nooobbbys1 game · 12.5% 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.
  • SnowCritter1 game · 12.5% of games in this matchup · Mean recorded OS 27.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.
  • Spooch1 game · 12.5% of games in this matchup · Mean recorded OS 15.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.
  • ziko1 game · 12.5% of games in this matchup · Mean recorded OS 14.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%.

Geo sea vs Beach sea

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

12 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,321.9 metal3,591.6 metal100.0%12 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.5,278.5 metal4,099.4 metal100.0%12 paired games
Energy producedTotal energy produced by this player by this time.59,269.7 energy38,708.2 energy100.0%12 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.1,392.5 damage904.1 damage100.0%12 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.898.9 damage1,195.6 damage100.0%12 paired games
Units producedTotal units produced by this time, including buildings.47.3 units34.7 units100.0%12 paired games
All units lostRecorded total units lost, including noncombat losses and buildings.2.8 units2.3 units50.0%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.74.8 metal185.6 metal100.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.228.2 metal79.7 metal100.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.2 units0.7 units100.0%12 paired games
  • Kbot_my_Ahole2 games · 16.7% of games in this matchup · Mean recorded OS 37.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.
  • Bestoloch1 game · 8.3% 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.
  • Ihatesea1 game · 8.3% of games in this matchup · Mean recorded OS 29.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.
  • KoolAid1 game · 8.3% of games in this matchup · Mean recorded OS 13.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.
  • mary_lou1 game · 8.3% of games in this matchup · Mean recorded OS 17.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.
  • ObeIix1 game · 8.3% of games in this matchup · Mean recorded OS 30.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.
  • ParadiseLost1 game · 8.3% of games in this matchup · Mean recorded OS 26.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.
  • Pelzor1 game · 8.3% of games in this matchup · Mean recorded OS 20.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.
  • smeet1 game · 8.3% of games in this matchup · Mean recorded OS 13.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.
  • spieriz1 game · 8.3% 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.
  • Taalibul_Ilm1 game · 8.3% of games in this matchup · Mean recorded OS 19.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.

Why some selected games have no identified lane:

  • No individual lane assigned for this position: 14 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.2 / 100

16 scored games · 80.0% coverage.

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

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

Why this score?

Beach sea

Supreme Isthmus v2.1 · Large teams · 16 players

54.5 / 100

12 scored games · 100.0% coverage.

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

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

Why this score?

Geo sea

Supreme Isthmus v2.1 · Large teams · 16 players

60.6 / 100

9 scored games · 69.2% coverage.

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

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

Why this score?

Geo tech

Supreme Isthmus v2.1 · Large teams · 16 players

55.1 / 100

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

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

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

Geo sea

13 selected games

Opens with Pawn 69.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. Pawn was the first observed fighting unit 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

Front (second)

19 selected games

Economy-focused at 10:00 60.0%

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 60% of comparable measured games. Matching comparison games available for 83.3% 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: 78.9%.
Explore this position

Beach sea

10 selected games

Opens with Riptide 80.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. Riptide was the first observed fighting unit start by 5:00 in 80% 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: 103 published games lasting at least five minutes, linked to account 501027. 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: 97.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, 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.