16 Mar 2026, 23:26
[FuenlaBoys]CommandArena
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| Broken_Soul | 190 | 56 | 93 | 0 | 205 | 58.3 cm | 0.60 | 38% | 28% | 0:07 |
| newut | 176 | 97 | 77 | 2 | 245 | - | 1.26 | 55% | 40% | 0:08 |
Red versus Blue balance for this match only.
Killer and victim pairings by team.
| Player | Double | Multi | Ultra | Monster | Ludicrous | Holy Shit | Best |
|---|---|---|---|---|---|---|---|
| -uh.StarzZz`- | 14 | 4 | 3 kills | ||||
| newut | 9 | 3 | 2 | 5 kills | |||
| -cide- | 11 | 4 | 3 kills | ||||
Loading player feedback...
Generated from the match events and player statistics.
A decisive game of 4v3 Instagib CTF took place on CTF-UH-CommandArena between Red and Blue Team, ending 2-11 in favour of Blue Team.
The opening breakthrough came at 0:13 when -cide- scored for Blue Team. Blue Team created more scoring chances, converting 11 of the 13 captures. The scoring pattern stayed relatively stable once the first lead was established. 7 captures were completed solo.
The final capture arrived at 9:30, with Broken_Soul finishing for Red Team on a solo run. That score set the closing shape of the match at 2-11.
-uh.StarzZz`- stood out as the main objective influence with 2 grabs, 1 capture, 21 returns, and an MVP score of 573. -uh.StarzZz`- made the biggest clutch contribution, recording 4 close-save returns.
Objective ledger for the match: 83 grabs, 18 pickups, 13 captures, 7 solos, 7 assists, 87 flag kills, 28 covers, 4 seals, 67 returns, 6 mid returns, 11 clutch returns, and 4 cherry picks.
-uh.StarzZz`- supplied the sharpest shooting numbers, finishing with 42% accuracy and 98 kills.
Community desk: -cide- triggered the UH Equinox file again, so imaslut is back in the match notes. 35 flag touches and 2 cherries means the cherry-picking bellend allegations remain extremely alive.
Cherry watch: -cide- logged 2 cherry picks, so the orchard was open and the complaints department has fresh material.
Blue Team ultimately secured the result through stronger capture conversion and late-game control.
| 167 |
| 77 |
| 82 |
| 1 |
| 279 |
| - |
| 0.94 |
| 48% |
| 33% |
| 0:08 |
| pato^ | - | - | - | - | - | - | - | - | - | - |
| Team Total | 533 | 230 | 252 | 3 | 729 | 58.3 cm | 0.91 | 48% | 34% | 0:24 |
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| -uh.StarzZz`- | 275 | 98 | 76 | 2 | 235 | 13.5 cm | 1.29 | 56% | 42% | 0:08 |
| -cide- | 261 | 88 | 79 | 0 | 219 | 46.0 cm | 1.11 | 53% | 40% | 0:08 |
| pato^ | 137 | 66 | 75 | 2 | 248 | - | 0.88 | 46% | 35% | 0:08 |
| Team Total | 673 | 252 | 230 | 4 | 702 | 29.7 cm | 1.10 | 52% | 39% | 0:26 |
Click the coloured player buttons to show or hide lines. Each line finishes on the same Equinox MVP score shown in the CTF MVP table.
Dots are timed MVP-impact events from this match. Captures still keep their deeper run details in the existing capture graph.
| 11 |
| 2 |
| 3 kills |
| pato^ | 9 | 3 | 3 kills |
| Broken_Soul | 5 | 1 | 3 kills |
| Player | Killing Spree | Rampage | Dominating | Unstoppable | Godlike | Best |
|---|---|---|---|---|---|---|
| -uh.StarzZz`- | 2 | 8 kills | ||||
| newut | 2 | 6 kills | ||||
| -cide- | 1 | 6 kills | ||||
| -uh.Pr3DazZz | 1 | 5 kills | ||||
| pato^ | 4 kills | |||||
| Broken_Soul | 4 kills |
Final Equinox gain: Match Score plus flag-run, objective, defensive baseline, shared team, and personal penalty adjustments.
| Rank | Player | Role | Grabs | Caps | Assists | Solos | Flag Kills | Def FK/BNS | Flag Run | Pickups | Covers | Mid Returns | Cherries | Returns | CLUTCH | MVP Score |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| - | -uh.StarzZz`- | Defender | 2 | 1 | 1 | 0 | 0 | 26/7 | 0 | 2 | 9 | 1 | 0 | 21 | 4 | 573 |
| - | -cide- | Attacker | 28 | 7 | 4 | 5 | 9 | 0/- | 0 | 7 | 5 | 1 | 2 | 8 | 0 | 428 |
| - | -uh.Pr3DazZz | Attacker | 16 | 1 | 0 | 1 | 13 | 0/- | 0 | 0 | 2 | 2 | 1 | 10 | 3 | 342 |
| - |
| Attacker |
| 13 |
| 0 |
| 0 |
| 0 |
| 18 |
| 0/- |
| 0 |
| 4 |
| 3 |
| 1 |
| 0 |
| 11 |
| 0 |
| 304 |
| - | pato^ | Attacker | 17 | 3 | 2 | 0 | 3 | 0/- | 0 | 4 | 8 | 0 | 0 | 3 | 0 | 249 |
| - | Broken_Soul | Attacker | 7 | 1 | 0 | 1 | 18 | 0/- | 0 | 1 | 1 | 1 | 1 | 14 | 4 | 244 |
| - | pato^ | Defender | 0 | 0 | 0 | 0 | 0 | 0/- | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 47 |
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 |
|---|---|---|---|---|---|---|---|---|---|
| Broken_Soul | 20000 | - | - | 22 | 22 | 23 | 0 | Good connection | |
| -uh.Pr3DazZz | 20000 | - | - | 11 | 11 | 12 | 0 | Good connection | |
| newut | 30000 | 0 | 240Hz | 93 | 95 | 97 | 0 | Good connection | |
| -uh.StarzZz`- | 30000 | 238 | 238Hz | 18 | 18 | 18 | 0 | Good connection | |
| pato^ | 20000 | - | - | 32 | 33 | 36 | 0 | Minor variation | |
| -cide- | 30000 | 360 | 240Hz | 23 | 24 | 25 | 0 | Good connection |
Match feedback based on the player's usual level and their role in this game.
| Player | Verdict | Role | Performance Notes |
|---|---|---|---|
| -cide- | Godlike | Attacker | This was excellent work from you, with your match rating landing at 2.06x. Your attacking play was strong, especially because you turned 28 grabs into 7 caps and 5 solos. Aim was a real positive at 40% accuracy, so keep taking fights where that strength matters. Your aggression is useful, but chancing it alone will often turn a good idea into a cheap death. |
| -uh.StarzZz`- | Godlike | Defender | You made a clear difference in this match and finished well above your normal level at 1.72x. Your defensive timing was good: 1 mid return and 4 clutch returns cut off runs at important moments. You fought efficiently: 98-76 with a 1.29 K/D, and I think you played your role in the team well. Next focus: protect your own flag first, then help the carrier survive with cover when the chance is there. |
| pato^ | Dominating | Attacker | You were sharp in this match and pushed above your usual level at 1.23x. You were dangerous with the flag: 17 grabs led to 3 caps. You gave your teammates good cover, so keep looking for those moments where your positioning keeps a run alive. Next focus: keep attacking, but work with your teammates more and use cover effectively so your runs last longer. |
| Broken_Soul | Dominating | Attacker | You gave your team more than expected here and finished at 1.21x. Your flag work was one of your best areas, with 7 grabs producing 1 cap and 1 solo. I think survival was your main issue: 56-93 means you died too often before you could put enough pressure on the enemy or help your team objective. Keep the fast grabs in your game, just make sure they are backed by cover instead of chancing it. |
| -uh.Pr3DazZz | Dominating | Attacker | You played well and finished above your usual level at 1.17x. Very strong flag running: you made 16 grabs count with 1 cap and 1 solo. You did make some good returns, and those stops helped your team stay in the game. Keep the fast grabs in your game, just make sure they are backed by cover instead of chancing it. |
| newut | Dominating | Attacker | I think this was a good step up from your normal game, with a 1.15x rating. Your flag pressure was good with 13 grabs, and working closer with your team would make those grabs more dangerous. You fought efficiently: 97-77 with a 1.26 K/D, and I think you played your role in the team well. Next focus: turn grabs into team runs by calling the route earlier and waiting half a beat for cover. |
| pato^ | Feeding | Defender | You had a tough match at 0.04x, well below your usual level, but I think it is fixable. You had defensive involvement, but your next step is being first to the danger more often, not just reacting after the grab. Nothing in the stats was wildly good or bad, which means small improvements in timing, survival, and team support could move your rating up. Next focus: keep reading the incoming routes, but add more cover for your own returning carrier when the flag is safe. |