3 Aug 2026, 18:38
Deck16][
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | HSK | HSA% | TTL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Bonka | 24 | 25 | 41 | 1 | 57 | - | 0.61 | 37% | 47% | 8 | - | 0:14 |
| muchi | 6 | 6 | 12 | 0 | -21 | - | 0.50 | 33% | 0% | 0 | - | 0:13 |
| Player | Double | Multi | Ultra | Monster | Ludicrous | Holy Shit | Best |
|---|---|---|---|---|---|---|---|
| muchi | 1 | 2 kills | |||||
| Bonka | 1 | 1 | 3 kills |
| Player | Killing Spree | Rampage | Dominating | Unstoppable | Godlike | Best |
|---|---|---|---|---|---|---|
| muchi |
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.
Bonka produced the strongest overall performance, finishing with 24 score, 25 kills, and 37% efficiency.
Bonka led the fragging pace with 25 kills.
Bonka posted the best accuracy at 47%.
Banter read: Bonka produced the kind of combat line that makes people immediately ask for the next map.
Bonka hit 47% 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.
| 4 kills |
| Bonka | 3 kills |
Match feedback based on the player's usual level and their role in this game.
| Player | Verdict | Role | Performance Notes |
|---|---|---|---|
| Bonka | Godlike | Combat | Great game, this was a really strong performance from you at 1.47x. For DM/TDM, your next jump is turning more fights into map control rather than just isolated duels. 37% 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. |
| muchi | Struggling | Combat | You dipped below your usual level at 0.82x, but I think there are clear areas you can tighten next match. This was mostly about combat basics for you: win cleaner fights, keep better positions, and avoid giving away easy deaths. 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: stop gambling alone into bad positions and take fights from areas you can escape from. |
Red versus Blue balance for this match only.
Per-player kills by weapon for this match.
Per-player pickup control for this match.
| Player | AMP | BELT | PADS | ARMOR | HEALTH | VIALS | BOOTS | INVIS | REDEEMER | WEAPONS | AMMO | TOTAL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Bonka | 1 | 1 | 6 | 6 | 40 | 48 | ||||||
| muchi | 8 | 6 |
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.
| 13 |
| 21 |
| Totals | 1 | 1 | 14 | 12 | 53 | 69 |
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 |
|---|---|---|---|---|---|---|---|---|---|
| Bonka | - | - | - | 40 | 42 | 44 | 0 | Minor variation | |
| muchi | - | - | - | 42 | 54 | 78 | 0 | Variable ping |