Replay data updated 14 Oct 2026, 08:05 UTC · Daily update starts 01:00 UTC (03:00 Stockholm time)

Data updated 14 Oct, 08:05 UTC

Daily update starts 01:00 UTC (03:00 Stockholm time). Replay collection continues while the update is prepared.

‹ Find another player

Dipfit

Account 491346 · Published replay history across maps and positions.

Latest recorded OS
18.3
14 Oct 2026 · Large teams · 16 players
Recorded games
70
18 Jul 2026–14 Oct 2026 UTC
Maps played
27
Map versions counted separately
Compare with another player

OS over time

Ratings recorded at game start in the replays we have. OS means OpenSkill rating.

First recorded
19.17
Latest recorded
18.32
Change
-0.85
OS over timeRecorded ratings at game start. Use the game selector below to read individual values.17.718.920.121.322.518 Jul 2026, 00:23 UTC · OS 19.1718 Jul 2026, 00:50 UTC · OS 19.6518 Jul 2026, 01:09 UTC · OS 20.2118 Jul 2026, 01:41 UTC · OS 20.2120 Jul 2026, 01:18 UTC · OS 20.1720 Jul 2026, 23:54 UTC · OS 20.3425 Jul 2026, 00:16 UTC · OS 20.2925 Jul 2026, 00:40 UTC · OS 20.2925 Jul 2026, 01:07 UTC · OS 20.2225 Jul 2026, 18:43 UTC · OS 19.8825 Jul 2026, 18:56 UTC · OS 19.8825 Jul 2026, 19:23 UTC · OS 20.4926 Jul 2026, 04:04 UTC · OS 20.1529 Jul 2026, 02:06 UTC · OS 20.5301 Aug 2026, 01:41 UTC · OS 20.1401 Aug 2026, 02:07 UTC · OS 20.5001 Aug 2026, 02:40 UTC · OS 20.9401 Aug 2026, 22:51 UTC · OS 21.4701 Aug 2026, 23:18 UTC · OS 21.4704 Aug 2026, 23:16 UTC · OS 20.2910 Aug 2026, 21:23 UTC · OS 20.1710 Aug 2026, 22:05 UTC · OS 20.5910 Aug 2026, 22:48 UTC · OS 20.9511 Aug 2026, 00:16 UTC · OS 21.3511 Aug 2026, 16:48 UTC · OS 21.6912 Aug 2026, 04:06 UTC · OS 21.2612 Aug 2026, 14:32 UTC · OS 21.4713 Aug 2026, 00:04 UTC · OS 21.5913 Aug 2026, 00:35 UTC · OS 21.5914 Aug 2026, 04:33 UTC · OS 21.4414 Aug 2026, 05:03 UTC · OS 21.0922 Aug 2026, 22:13 UTC · OS 21.0222 Aug 2026, 23:29 UTC · OS 20.5822 Aug 2026, 23:57 UTC · OS 20.5723 Aug 2026, 00:23 UTC · OS 20.5726 Aug 2026, 01:38 UTC · OS 21.0726 Aug 2026, 02:00 UTC · OS 21.0726 Aug 2026, 13:01 UTC · OS 21.0126 Aug 2026, 13:30 UTC · OS 21.0126 Aug 2026, 13:39 UTC · OS 21.0127 Aug 2026, 00:23 UTC · OS 21.1027 Aug 2026, 00:47 UTC · OS 21.1027 Aug 2026, 01:05 UTC · OS 21.5028 Aug 2026, 00:15 UTC · OS 21.4728 Aug 2026, 00:55 UTC · OS 21.8928 Aug 2026, 01:29 UTC · OS 21.3228 Aug 2026, 02:43 UTC · OS 20.9028 Aug 2026, 02:58 UTC · OS 21.7431 Aug 2026, 23:25 UTC · OS 21.3101 Sep 2026, 20:57 UTC · OS 20.6801 Sep 2026, 22:17 UTC · OS 20.7901 Sep 2026, 22:56 UTC · OS 20.4501 Sep 2026, 23:27 UTC · OS 20.1105 Sep 2026, 22:50 UTC · OS 19.3705 Sep 2026, 23:13 UTC · OS 19.7905 Sep 2026, 23:45 UTC · OS 19.7906 Sep 2026, 00:06 UTC · OS 19.6806 Sep 2026, 23:39 UTC · OS 19.6007 Sep 2026, 00:11 UTC · OS 19.6016 Sep 2026, 00:56 UTC · OS 19.1208 Oct 2026, 23:52 UTC · OS 18.9109 Oct 2026, 00:26 UTC · OS 18.9112 Oct 2026, 01:19 UTC · OS 18.6512 Oct 2026, 02:44 UTC · OS 18.3214 Oct 2026, 00:54 UTC · OS 18.3218 Jul14 Oct

14 Oct 2026, 00:54 UTC · OS 18.32

65 recorded ratings · 18 Jul 2026–14 Oct 2026.

Game formats are shown separately.

Playstyle and score by position

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.

Habits: 15 Sep to 14 Oct 2026 UTC · Supreme Isthmus v2.1 · human 8v8 · mirrored starts combined. Checked 14 Oct 2026, 18:18 UTC.

Busiest positions first.

Not enough measured games yet in these positions

Recent activity

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

02026-09-17
to 2026-09-23
02026-09-24
to 2026-09-30
02026-10-01
to 2026-10-07
52026-10-08
to 2026-10-14

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

Selected games: 19 · Games with identified lanes: 15.

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

Beach sea vs Geo sea

10 matched games · 10 distinct opponents · Mean opponent OS 22.5.

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.

10 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.2,971.2 metal3,193.1 metal100.0%10 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,748.1 metal3,891.2 metal100.0%10 paired games
Energy producedTotal energy produced by this player by this time.36,344.7 energy44,160.4 energy100.0%10 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.3,196.5 damage893.2 damage100.0%10 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,404.8 damage1,692.8 damage100.0%10 paired games
Units producedTotal units produced by this time, including buildings.35.2 units37.8 units100.0%10 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.363.5 metal316.0 metal20.0%2 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.476.0 metal363.5 metal20.0%2 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.4.5 units1.0 units20.0%2 paired games
  • Alphacure1 game · 10.0% of games in this matchup · Mean recorded OS 28.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.
  • ArthurianKing1 game · 10.0% of games in this matchup · Mean recorded OS 22.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.
  • ChickenMan2771 game · 10.0% of games in this matchup · Mean recorded OS 24.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.
  • dachouf1 game · 10.0% of games in this matchup · Mean recorded OS 20.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.
  • DormantDVS19991 game · 10.0% of games in this matchup · Mean recorded OS 28.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.
  • iResc1 game · 10.0% of games in this matchup · Mean recorded OS 14.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.
  • JarDor1 game · 10.0% of games in this matchup · Mean recorded OS 27.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.
  • kingixdjames1 game · 10.0% of games in this matchup · Mean recorded OS 20.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.
  • Lizzycci891 game · 10.0% of games in this matchup · Mean recorded OS 11.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.
  • OneTrickPony1 game · 10.0% of games in this matchup · Mean recorded OS 28.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.

Front (second) vs Shared central front · shared frontline

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

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,323.2 metal4,322.2 metal100.0%3 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,796.2 metal4,012.2 metal100.0%3 paired games
Energy producedTotal energy produced by this player by this time.44,972.3 energy45,715.8 energy100.0%3 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.6,490.9 damage10,080.7 damage100.0%3 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.12,194.4 damage8,917.0 damage100.0%3 paired games
Units producedTotal units produced by this time, including buildings.32.0 units39.5 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.925.5 metal617.8 metal66.7%2 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.495.0 metal796.5 metal66.7%2 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.6.0 units3.2 units66.7%2 paired games
  • Boozha1 game · 33.3% of games in this matchup · Mean recorded OS 30.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.
  • Dieterling1 game · 33.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.
  • DontPanic521 game · 33.3% of games in this matchup · Mean recorded OS 12.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.
  • finstas1 game · 33.3% of games in this matchup · Mean recorded OS 12.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.
  • heart_attack1 game · 33.3% of games in this matchup · Mean recorded OS 34.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.
  • SauceDispenser1 game · 33.3% of games in this matchup · Mean recorded OS 33.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.

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

2 matched games · 4 distinct opponents · Mean opponent OS 16.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.

2 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,248.4 metal4,057.0 metal100.0%2 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,161.1 metal3,898.7 metal100.0%2 paired games
Energy producedTotal energy produced by this player by this time.39,092.7 energy46,373.6 energy100.0%2 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.10,123.4 damage4,833.5 damage100.0%2 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.7,757.0 damage6,228.6 damage100.0%2 paired games
Units producedTotal units produced by this time, including buildings.38.0 units40.5 units100.0%2 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.Not recordedNot recorded0.0%0 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.Not recordedNot recorded0.0%0 paired games
Fighting units lost to enemiesCompleted fighting units lost to enemies: bots, vehicles, aircraft and ships. Excludes commanders, builders and buildings.Not recordedNot recorded0.0%0 paired games
  • ArthurianKing1 game · 50.0% of games in this matchup · Mean recorded OS 22.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.
  • Maverickgk1 game · 50.0% of games in this matchup · Mean recorded OS 6.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.
  • UltimoDealer1 game · 50.0% 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.
  • Whackolyte1 game · 50.0% of games in this matchup · Mean recorded OS 16.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.

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

Why some selected games have no identified lane:

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

Ask about this player

Open a prepared question for Supreme Isthmus v2.1, then adjust the map, position, game version or reference rating.

About these results

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