Unreal HeavenThe home of 2v2 and 3v3 iCTF3 Aug 2026, 18:05
Deck16][
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | HSK | HSA% | TTL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dystroit_123 | 15 | 15 | 30 | 0 | 47 | - | 0.50 | 33% | 67% | 7 | - | 0:09 |
| fdf | 0 | 0 | 0 | 0 | - | - | 0 | 0% | 0% | 0 | - | 0:00 |
| Krokus | 0 | 0 | 17 | 0 | 49 | - | 0.00 | 0% | 0% | 0 | - | 0:10 |
Loading player feedback...
Generated from the match events and player statistics.
A tight NW DM match took place on DM-Deck16][-UH, with 3 active players recorded in the report.
dystroit_123 produced the strongest overall performance, finishing with 15 score, 15 kills, and 33% efficiency.
dystroit_123 led the fragging pace with 15 kills.
dystroit_123 posted the best accuracy at 67%.
Banter read: dystroit_123 made the table look personal with 15 score and 33% efficiency.
dystroit_123 hit 67% accuracy, which is exactly the kind of number that creates three separate lag excuses.
The final table reflects the players who converted pressure most consistently across the match.
Match feedback based on the player's usual level and their role in this game.
| Player | Verdict | Role | Performance Notes |
|---|---|---|---|
| dystroit_123 | Godlike | Combat | Well played, this was a fantastic performance at 3.00x. Your influence came through fighting, so the big levers are efficiency, positioning, and staying near useful areas of the map. 33% efficiency hurt you here; I think the priority is taking fewer low-percentage fights and resetting before you are forced into bad trades. Next focus: value your life more, reset from weak fights, and make the enemy work harder for every frag. |
| fdf | Feeding | Combat | This was a hard outing for you at 0.00x; treat it as a reset point, not a verdict on your ability. For DM/TDM, your next jump is turning more fights into map control rather than just isolated duels. 0% efficiency hurt you here; I think the priority is taking fewer low-percentage fights and resetting before you are forced into bad trades. Next focus: value your life more, reset from weak fights, and make the enemy work harder for every frag. |
| Krokus | Feeding | Combat | You had a rough game at 0.00x, so I think your goal should be to simplify and rebuild from safer plays. For DM/TDM, your next jump is turning more fights into map control rather than just isolated duels. 0% efficiency hurt you here; I think the priority is taking fewer low-percentage fights and resetting before you are forced into bad trades. Next focus: avoid chancing it into stacked players; wait for armour, a better weapon, or a teammate before re-engaging. |
Red versus Blue balance for this match only.
Per-player kills by weapon for this match.
| Player | Total | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| dystroit_123 | 2 | 3 | 10 | 15 | ||||||
| Totals | 2 | 3 | 10 | 15 |
Per-player pickup control for this match.
| Player | AMP | BELT | PADS | ARMOR | HEALTH | VIALS | BOOTS | INVIS | REDEEMER | WEAPONS | AMMO | TOTAL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dystroit_123 | 1 | 31 | 32 | |||||||||
| Krokus |
Weapon kills and pickup control for this match only.
Red vs Blue armor, pads, belt, and amp control for this match.
Click the coloured player buttons to show or hide lines. Hover dots for killer, victim, and match time.
Each coloured line is a player. Hover dots to see which pickup they collected.
Dots are real headshot events from combat_events. Warmup is hidden; extra time is shown when needed.
Pickup Control graph is unchanged. This line graph shows timed pickups where raw pickup events are available.
| 18 |
| 18 |
| fdf |
| Totals | 1 | 49 | 50 |
Kills by weapon in this match.
Best player and weapon pairings in this match.
Different summary from the timeline graph: pickup types, power pickups, and first/last control moments.
Uses the match ngLog and UHNet connection values: client NetSpeed, client FPS when logged, and ping samples across the match. Min, Avg and Max summarise the ping range, the trace shows the connection pattern, and spikes mark sudden jumps.
| Player | Client NetSpeed | Client FPS | Refresh | Min | Avg | Max | Spikes | Ping Trace | Pattern |
|---|---|---|---|---|---|---|---|---|---|
| dystroit_123 | - | - | - | 73 | 98 | 191 | 5 | Unstable spikes | |
| Krokus | - | - | - | 53 | 57 | 70 | 2 | Occasional lag spikes |