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

Epyx

Account 111624 · Published replay history across maps and positions.

Latest recorded OS
37.5
27 Jul 2026 · Large teams · 16 players
Recorded games
104
27 Jun 2026–27 Jul 2026 UTC
Maps played
1
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.

Large teams · 16 players

First recorded
34.65
Latest recorded
37.45
Change
+2.80
OS over timeRecorded ratings at game start. Use the game selector below to read individual values.33.635.236.938.540.127 Jun 2026, 22:56 UTC · OS 34.6528 Jun 2026, 00:55 UTC · OS 34.6528 Jun 2026, 01:26 UTC · OS 34.6528 Jun 2026, 01:56 UTC · OS 34.6528 Jun 2026, 02:16 UTC · OS 34.6528 Jun 2026, 02:44 UTC · OS 34.6528 Jun 2026, 05:56 UTC · OS 35.1929 Jun 2026, 11:59 UTC · OS 35.1929 Jun 2026, 12:36 UTC · OS 35.1929 Jun 2026, 22:01 UTC · OS 34.9929 Jun 2026, 23:18 UTC · OS 34.4329 Jun 2026, 23:51 UTC · OS 34.4330 Jun 2026, 00:12 UTC · OS 34.4330 Jun 2026, 00:43 UTC · OS 34.4330 Jun 2026, 12:41 UTC · OS 35.0001 Jul 2026, 04:53 UTC · OS 35.5001 Jul 2026, 05:17 UTC · OS 35.5001 Jul 2026, 05:36 UTC · OS 35.5001 Jul 2026, 06:04 UTC · OS 35.5001 Jul 2026, 07:18 UTC · OS 35.5001 Jul 2026, 07:39 UTC · OS 35.5001 Jul 2026, 08:00 UTC · OS 35.5001 Jul 2026, 08:35 UTC · OS 35.5001 Jul 2026, 08:55 UTC · OS 35.5001 Jul 2026, 09:40 UTC · OS 35.5001 Jul 2026, 10:01 UTC · OS 35.5001 Jul 2026, 10:31 UTC · OS 35.5001 Jul 2026, 10:59 UTC · OS 35.5001 Jul 2026, 11:30 UTC · OS 35.5002 Jul 2026, 08:48 UTC · OS 35.8602 Jul 2026, 09:31 UTC · OS 35.6103 Jul 2026, 14:25 UTC · OS 35.8304 Jul 2026, 09:17 UTC · OS 36.4304 Jul 2026, 09:48 UTC · OS 36.4304 Jul 2026, 21:33 UTC · OS 36.7004 Jul 2026, 22:03 UTC · OS 36.7004 Jul 2026, 22:26 UTC · OS 36.7004 Jul 2026, 22:55 UTC · OS 36.7004 Jul 2026, 23:09 UTC · OS 36.7004 Jul 2026, 23:25 UTC · OS 36.7005 Jul 2026, 10:49 UTC · OS 36.6006 Jul 2026, 22:25 UTC · OS 36.4006 Jul 2026, 22:44 UTC · OS 36.4006 Jul 2026, 23:22 UTC · OS 36.4207 Jul 2026, 00:14 UTC · OS 36.7107 Jul 2026, 00:35 UTC · OS 36.7107 Jul 2026, 00:50 UTC · OS 36.7109 Jul 2026, 22:42 UTC · OS 37.2209 Jul 2026, 23:19 UTC · OS 37.2210 Jul 2026, 09:50 UTC · OS 37.4610 Jul 2026, 20:55 UTC · OS 37.7710 Jul 2026, 21:10 UTC · OS 37.7710 Jul 2026, 21:37 UTC · OS 37.7711 Jul 2026, 19:03 UTC · OS 36.6411 Jul 2026, 19:23 UTC · OS 36.6411 Jul 2026, 20:41 UTC · OS 36.6411 Jul 2026, 20:52 UTC · OS 36.6411 Jul 2026, 21:16 UTC · OS 36.6411 Jul 2026, 22:53 UTC · OS 36.6412 Jul 2026, 23:15 UTC · OS 37.1913 Jul 2026, 00:19 UTC · OS 36.9613 Jul 2026, 00:56 UTC · OS 36.9613 Jul 2026, 19:40 UTC · OS 37.5313 Jul 2026, 19:58 UTC · OS 37.5313 Jul 2026, 20:23 UTC · OS 37.5313 Jul 2026, 20:46 UTC · OS 37.5313 Jul 2026, 21:09 UTC · OS 37.5314 Jul 2026, 20:15 UTC · OS 37.3614 Jul 2026, 20:51 UTC · OS 37.6114 Jul 2026, 21:07 UTC · OS 37.6114 Jul 2026, 21:26 UTC · OS 37.6114 Jul 2026, 22:11 UTC · OS 37.6114 Jul 2026, 23:10 UTC · OS 37.7015 Jul 2026, 01:13 UTC · OS 37.7015 Jul 2026, 21:53 UTC · OS 37.0515 Jul 2026, 23:00 UTC · OS 36.7916 Jul 2026, 00:00 UTC · OS 36.9816 Jul 2026, 01:03 UTC · OS 36.9216 Jul 2026, 01:38 UTC · OS 37.1716 Jul 2026, 02:13 UTC · OS 37.1716 Jul 2026, 14:24 UTC · OS 37.1316 Jul 2026, 22:32 UTC · OS 37.4218 Jul 2026, 01:05 UTC · OS 37.9818 Jul 2026, 01:33 UTC · OS 37.9818 Jul 2026, 02:37 UTC · OS 37.9818 Jul 2026, 02:54 UTC · OS 37.9818 Jul 2026, 03:20 UTC · OS 37.9820 Jul 2026, 16:58 UTC · OS 39.2720 Jul 2026, 21:01 UTC · OS 38.5720 Jul 2026, 21:36 UTC · OS 38.5720 Jul 2026, 22:05 UTC · OS 37.9620 Jul 2026, 22:41 UTC · OS 37.9622 Jul 2026, 13:32 UTC · OS 37.7423 Jul 2026, 21:39 UTC · OS 37.4023 Jul 2026, 22:09 UTC · OS 37.4023 Jul 2026, 22:25 UTC · OS 36.9423 Jul 2026, 22:48 UTC · OS 36.9426 Jul 2026, 22:11 UTC · OS 37.6126 Jul 2026, 23:04 UTC · OS 37.6127 Jul 2026, 17:08 UTC · OS 37.4527 Jul 2026, 17:20 UTC · OS 37.4527 Jul 2026, 17:45 UTC · OS 37.4527 Jul 2026, 18:23 UTC · OS 37.4527 Jul 2026, 18:44 UTC · OS 37.4527 Jun27 Jul

27 Jul 2026, 18:44 UTC · OS 37.45

104 recorded ratings · 27 Jun 2026–27 Jul 2026.

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.

No habits to show yet. Habits come from Supreme Isthmus v2.1 human 8v8 games between 15 Sep and 14 Oct 2026 (UTC), with at least 10 measured games in a position. This player has none in that period.

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

Selected games: 104 · Games with identified lanes: 59.

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

Beach sea vs Geo sea

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

4 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,573.2 metal4,046.0 metal100.0%4 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,810.4 metal4,685.0 metal100.0%4 paired games
Energy producedTotal energy produced by this player by this time.29,119.3 energy46,370.6 energy100.0%4 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.955.2 damage1,128.2 damage100.0%4 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,539.5 damage897.7 damage100.0%4 paired games
Units producedTotal units produced by this time, including buildings.29.5 units47.5 units100.0%4 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
  • 01xiam1 game · 25.0% of games in this matchup · Mean recorded OS 20.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.
  • [MADO]Malik1 game · 25.0% of games in this matchup · Mean recorded OS 32.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.
  • hihimik1 game · 25.0% of games in this matchup · Mean recorded OS 30.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.
  • Leohvm1 game · 25.0% of games in this matchup · Mean recorded OS 53.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.

Front (second) vs Shared central front · shared frontline

1 matched game · 2 distinct opponents · Mean opponent OS 35.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.

1 game 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,632.9 metal3,459.0 metal100.0%1 paired game
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,469.7 metal4,105.7 metal100.0%1 paired game
Energy producedTotal energy produced by this player by this time.43,137.5 energy44,544.4 energy100.0%1 paired game
Damage dealtRecorded damage dealt across the match, including fights outside this lane.7,610.1 damage9,953.0 damage100.0%1 paired game
Damage receivedRecorded damage received across the match, including fights outside this lane.9,208.0 damage7,691.8 damage100.0%1 paired game
Units producedTotal units produced by this time, including buildings.45.0 units45.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.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
  • Adeus1 game · 100.0% of games in this matchup · Mean recorded OS 33.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.
  • Spreukenindekeuken1 game · 100.0% of games in this matchup · Mean recorded OS 37.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.

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

1 matched game · 2 distinct opponents · Mean opponent OS 28.6.

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.

1 game 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,329.9 metal4,142.4 metal100.0%1 paired game
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.3,998.7 metal3,881.6 metal100.0%1 paired game
Energy producedTotal energy produced by this player by this time.46,581.0 energy41,290.6 energy100.0%1 paired game
Damage dealtRecorded damage dealt across the match, including fights outside this lane.7,752.9 damage7,774.7 damage100.0%1 paired game
Damage receivedRecorded damage received across the match, including fights outside this lane.10,115.2 damage8,401.0 damage100.0%1 paired game
Units producedTotal units produced by this time, including buildings.51.0 units41.5 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.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
  • Rysica1 game · 100.0% of games in this matchup · Mean recorded OS 36.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.
  • ThuddyDrumms1 game · 100.0% of games in this matchup · Mean recorded OS 21.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.

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

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

53 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,901.3 metal3,562.7 metal100.0%53 paired games
Metal spentRecorded spending when available, otherwise the published resource-balance reconstruction.4,570.8 metal4,158.4 metal100.0%53 paired games
Energy producedTotal energy produced by this player by this time.38,688.3 energy38,669.0 energy100.0%53 paired games
Damage dealtRecorded damage dealt across the match, including fights outside this lane.911.7 damage1,329.7 damage100.0%53 paired games
Damage receivedRecorded damage received across the match, including fights outside this lane.1,185.4 damage871.3 damage100.0%53 paired games
Units producedTotal units produced by this time, including buildings.34.0 units35.4 units100.0%53 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
  • Rysica4 games · 7.5% of games in this matchup · Mean recorded OS 37.6Profile owner’s team won 25.0% of games with a known result; result coverage 100.0%. This is a team result, not a duel result.
  • Damsko2 games · 3.8% of games in this matchup · Mean recorded OS 39.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.
  • Erilium2 games · 3.8% of games in this matchup · Mean recorded OS 49.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.
  • Hummell2 games · 3.8% of games in this matchup · Mean recorded OS 40.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.
  • [APM]Sanae_Kochiya1 game · 1.9% of games in this matchup · Mean recorded OS 52.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.
  • [Fx]DoodVanDaag1 game · 1.9% of games in this matchup · Mean recorded OS 32.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.
  • [IF]Yoshii1 game · 1.9% of games in this matchup · Mean recorded OS 17.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.
  • Anacondaq1 game · 1.9% of games in this matchup · Mean recorded OS 17.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.
  • anon_ze1 game · 1.9% of games in this matchup · Mean recorded OS 21.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.
  • arcsiz1 game · 1.9% of games in this matchup · Mean recorded OS 32.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.
  • AzurePure1 game · 1.9% of games in this matchup · Mean recorded OS 21.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.
  • BachMate1 game · 1.9% 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.
  • badbot1 game · 1.9% 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.
  • bahlomator1 game · 1.9% 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.
  • BardUp1 game · 1.9% of games in this matchup · Mean recorded OS 29.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.
  • Beenami1 game · 1.9% of games in this matchup · Mean recorded OS 29.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.
  • Boomer911 game · 1.9% of games in this matchup · Mean recorded OS 16.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.
  • CaptainCanada1 game · 1.9% of games in this matchup · Mean recorded OS 19.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.
  • enderOS11 game · 1.9% of games in this matchup · Mean recorded OS 32.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.
  • EtherealStrider1 game · 1.9% 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.

Showing 20 of 47 recorded opponents.

Why some selected games have no identified lane:

  • Starting layout not verified: 3 games.
  • No individual lane assigned for this position: 41 games.
  • Starting-position records unavailable: 1 game.

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