Replay data published 9 Oct 2026, 06:28 · Daily update starts 03:00 Stockholm time

Sadist1

Account 207796 · Published replay history across maps and positions.

Latest recorded OS
23.4
08 Oct 2026 · Large teams · 16 players
Recorded games
25
26 Sep 2026–08 Oct 2026 UTC
Maps played
2
Map versions counted separately

OS over time

Ratings recorded at game start in the replays we have.

Large teams · 16 players

First recorded
24.65
Latest recorded
23.44
Change
-1.21
OS over timeRecorded ratings at game start. Use the game selector below to read individual values.22.923.924.925.926.926 Sep 2026, 05:40 UTC · OS 24.6526 Sep 2026, 06:15 UTC · OS 24.3226 Sep 2026, 14:16 UTC · OS 24.6701 Oct 2026, 15:28 UTC · OS 26.4101 Oct 2026, 15:57 UTC · OS 25.6101 Oct 2026, 16:16 UTC · OS 25.6101 Oct 2026, 16:46 UTC · OS 25.6102 Oct 2026, 15:30 UTC · OS 25.1202 Oct 2026, 16:03 UTC · OS 25.1202 Oct 2026, 16:21 UTC · OS 24.7602 Oct 2026, 16:36 UTC · OS 24.7605 Oct 2026, 14:58 UTC · OS 25.4705 Oct 2026, 15:20 UTC · OS 25.4706 Oct 2026, 14:02 UTC · OS 25.0306 Oct 2026, 14:26 UTC · OS 25.0306 Oct 2026, 15:40 UTC · OS 24.3106 Oct 2026, 16:14 UTC · OS 24.3107 Oct 2026, 15:52 UTC · OS 24.2807 Oct 2026, 16:35 UTC · OS 24.2807 Oct 2026, 17:44 UTC · OS 24.2807 Oct 2026, 17:57 UTC · OS 24.2808 Oct 2026, 12:47 UTC · OS 23.4408 Oct 2026, 14:17 UTC · OS 23.4408 Oct 2026, 14:48 UTC · OS 23.4408 Oct 2026, 15:01 UTC · OS 23.4426 Sep08 Oct

08 Oct 2026, 15:01 UTC · OS 23.44

25 recorded ratings · 26 Sep 2026–08 Oct 2026.

Recorded playstyle traits

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-10–2026-10-09 UTC · Supreme Isthmus v2.1 · human 8v8 · mirrored starts combined. Checked 09 Oct 2026, 23:53 UTC.

Front (suicide)

13 selected games

Opens with Tick 84.6%
Explanation and coverage

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 84.6% 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

Recent activity

Recorded games in the last four weeks. This shows activity, not a change in skill. Imports may be incomplete.

02026-09-12
to 2026-09-18
02026-09-19
to 2026-09-25
112026-09-26
to 2026-10-02
142026-10-03
to 2026-10-09

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: 100.0% of selected games.

Selected games: 16 · Games with identified lanes: 16.

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

Front (second) vs Shared central front · shared frontline

3 matched games · 6 distinct opponents · Mean opponent OS 20.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.

3 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,338.8 metal3,738.7 metal100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,695.1 metal3,994.2 metal100.0%3 paired games
Energy producedTotal energy produced by this player by this time.45,009.0 energy50,673.9 energy100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.7,776.1 damage13,479.9 damage100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.7,826.2 damage11,034.1 damage100.0%3 paired games
Units producedTotal units produced by this time, including buildings.35.3 units41.8 units100.0%3 paired games
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.1,726.7 metal1,875.5 metal100.0%3 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,129.3 metal1,292.5 metal100.0%3 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.7.0 units5.7 units100.0%3 paired games
  • Etherift1 game · 33.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.
  • gflow1 game · 33.3% of games in this matchup · Mean recorded OS 23.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.
  • Hades_1 game · 33.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.
  • mlem861 game · 33.3% of games in this matchup · Mean recorded OS 25.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.
  • Sujiro_Kimimame1 game · 33.3% of games in this matchup · Mean recorded OS 13.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.
  • weakend1 game · 33.3% of games in this matchup · Mean recorded OS 6.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%.

Front (suicide) vs Shared central front · shared frontline

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

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,624.6 metal3,777.2 metal100.0%13 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,963.5 metal4,342.3 metal100.0%13 paired games
Energy producedTotal energy produced by this player by this time.44,669.4 energy52,098.4 energy100.0%13 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.9,148.0 damage7,331.2 damage100.0%13 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.7,927.4 damage8,527.4 damage100.0%13 paired games
Units producedTotal units produced by this time, including buildings.42.2 units47.4 units100.0%13 paired games
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.1,042.1 metal740.6 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,109.6 metal908.5 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.3.9 units5.5 units92.3%12 paired games
  • Sevendcell3 games · 23.1% 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.
  • smeet3 games · 23.1% of games in this matchup · Mean recorded OS 11.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.
  • zzxnb2 games · 15.4% of games in this matchup · Mean recorded OS 6.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.
  • [BS]_Gremlin1 game · 7.7% 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.
  • [Crd]OliverSton31 game · 7.7% 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.
  • Azzap1 game · 7.7% of games in this matchup · Mean recorded OS 16.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.
  • dmdm1 game · 7.7% 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.
  • Fergs1 game · 7.7% of games in this matchup · Mean recorded OS 18.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.
  • gflow1 game · 7.7% of games in this matchup · Mean recorded OS 23.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.
  • Green_Jinjo1 game · 7.7% of games in this matchup · Mean recorded OS 17.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.
  • gy0h6y1 game · 7.7% of games in this matchup · Mean recorded OS 32.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.
  • jacknight291 game · 7.7% of games in this matchup · Mean recorded OS 14.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.
  • Mastroideo1 game · 7.7% of games in this matchup · Mean recorded OS 12.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.
  • micia1 game · 7.7% of games in this matchup · Mean recorded OS 23.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.
  • parpax1 game · 7.7% of games in this matchup · Mean recorded OS 2.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.
  • PiedmontBell1 game · 7.7% of games in this matchup · Mean recorded OS 22.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.
  • Qlindex1 game · 7.7% 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.
  • Schnitzel_von_Wagen1 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.
  • TheSupportGod1 game · 7.7% of games in this matchup · Mean recorded OS 11.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.
  • WobblyCommander1 game · 7.7% 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.

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

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.

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: 25 published games lasting at least five minutes, linked to account 207796. 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: 100.0% 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 09 Oct 2026, 04:50 UTC; this summary prepared 09 Oct 2026, 06:14 UTC. Traits and daily rankings can have different update times. Imports are not a complete archive of every BAR match.