Unreal HeavenThe home of 2v2 and 3v3 iCTF4 Aug 2026, 16:16
Deck16][
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | HSK | HSA% | TTL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dim | 50 | 52 | 28 | 2 | 198 | - | 1.86 | 63% | 42% | 13 | - | 0:32 |
| Xar | 0 | 0 | 0 | 0 | - | - | 0 | 0% | 0% | 0 | - | 0:00 |
| Player | Double | Multi | Ultra | Monster | Ludicrous | Holy Shit | Best |
|---|---|---|---|---|---|---|---|
| dim | 4 | 2 kills |
| Player | Killing Spree | Rampage | Dominating | Unstoppable | Godlike | Best |
|---|---|---|---|---|---|---|
| dim | 3 | 8 kills |
Loading player feedback...
Generated from the match events and player statistics.
A tight NW DM match took place on DM-Deck16][-UH, with 2 active players recorded in the report.
dim produced the strongest overall performance, finishing with 50 score, 52 kills, and 63% efficiency.
dim led the fragging pace with 52 kills.
dim posted the best accuracy at 42%.
Banter read: dim made the table look personal with 50 score and 63% efficiency.
dim hit 42% 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 |
|---|---|---|---|
| dim | Godlike | Combat | You played a really good game here and your 1.92x rating shows it. You played the fragging side well here, putting pressure on the enemy while keeping your own deaths under control. 63% efficiency is a strong sign that you picked good fights and stayed alive after winning them. Next focus: keep the fragging up, but make the kills happen around weapons, armour, belt, and routes your team needs. |
| Xar | Feeding | Combat | This was a hard outing for you at 0.00x; treat it as a reset point, not a verdict on your ability. This was mostly about combat basics for you: win cleaner fights, keep better positions, and avoid giving away easy deaths. 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 | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| dim | 15 | 9 | 4 | 19 | 47 | |||||
| Totals | 15 | 9 | 4 | 19 | 47 |
Per-player pickup control for this match.
| Player | AMP | BELT | PADS | ARMOR | HEALTH | VIALS | BOOTS | INVIS | REDEEMER | WEAPONS | AMMO | TOTAL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dim | 2 | 5 | 12 | 38 | 26 | 6 | 43 | 98 | ||||
| Xar |
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.
| Totals | 2 | 5 | 12 | 38 | 26 | 6 | 43 | 98 |
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.
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.
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 |
|---|---|---|---|---|---|---|---|---|---|
| dim | - | - | - | 42 | 51 | 164 | 2 | Occasional lag spikes |