Unreal HeavenThe home of 2v2 and 3v3 iCTF4 Dec 2025, 22:14
CTF-ThornsV2_Small
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| 295 | 99 | 119 | 0 | 272 | 20.3 cm | 0.83 | 45% | 36% | 0:05 | |
| 260 | 112 | 112 | 0 | 299 | 13.5 cm | 1.00 | 50% | 41% | 0:05 | |
| Team Total |
Red versus Blue balance for this match only.
Killer and victim pairings by team.
| Killer | Victim | |
|---|---|---|
| 58 | ||
| 41 | ||
| 60 | ||
| 52 |
| Killer | Victim | |
|---|---|---|
| 69 | ||
| 56 | ||
| 50 | ||
| 56 |
| Player | Double | Multi | Ultra | Monster | Ludicrous | Holy Shit | Best |
|---|---|---|---|---|---|---|---|
| 15 | 4 | 1 | 1 | 5 kills | |||
| 23 | 6 | 3 | 4 kills | ||||
| 13 | 3 | 1 | 4 kills | ||||
Loading player feedback...
Generated from the match events and player statistics.
A decisive game of 2v2 Instagib CTF took place on CTF-ThornsV2_Small between Red and Blue Team, ending 11-3 in favour of Red Team.
The opening breakthrough came at 1:05 when pho` scored for Red Team. Red Team created more scoring chances, converting 11 of the 14 captures. The scoring pattern stayed relatively stable once the first lead was established. 10 captures were completed solo.
The final capture arrived at 10:37, with pho` finishing for Red Team on a solo run. That score set the closing shape of the match at 11-3.
pho` stood out as the main objective influence with 19 grabs, 6 captures, 9 returns, and an MVP score of 1115. pho` made the biggest clutch contribution, recording 3 close-save returns.
Objective ledger for the match: 60 grabs, 14 pickups, 14 captures, 9 solos, 4 assists, 59 flag kills, 25 covers, 0 seals, 44 returns, 38 mid returns, 6 clutch returns, and 0 cherry picks.
_-=Pr3dazZz=- supplied the sharpest shooting numbers, finishing with 41% accuracy and 125 kills.
Community desk: pho` brought number-one pug-bot-captain energy into the report, which means at least one decision probably came with a draft explanation and a queue argument.
Clutch desk: pho` produced 3 close-save returns, also known as deleting someone else's highlight clip.
Red Team ultimately secured the result through stronger capture conversion and late-game control.
| 555 |
| 211 |
| 231 |
| 0 |
| 571 |
| 16.9 cm |
| 0.91 |
| 48% |
| 39% |
| 0:12 |
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| 252 | 125 | 118 | 0 | 339 | 36.0 cm | 1.06 | 51% | 41% | 0:05 | |
| 227 | 106 | 93 | 0 | 311 | - | 1.14 | 53% | 37% | 0:07 | |
| Team Total | 479 | 231 | 211 | 0 | 650 | 36.0 cm | 1.09 | 52% | 39% | 0:13 |
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.
| 16 |
| 6 |
| 2 |
| 4 kills |
| Player | Killing Spree | Rampage | Dominating | Unstoppable | Godlike | Best |
|---|---|---|---|---|---|---|
| 2 | 8 kills | |||||
| 1 | 5 kills | |||||
| 1 | 5 kills | |||||
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| -🇬🇧 | Attacker | 19 | 6 | 2 | 5 | 13 | 0/- | 666 | 2 | 2 | 7 | 0 | 9 | 3 | 1115 | |
| -🇬🇧 | Attacker | 20 | 5 | 1 | 2 | 10 | 0/- | 434 | 6 | 15 | 6 | 0 | 8 | 1 | 892 | |
| -🇬🇧 | Attacker | 20 | 1 | 1 | 1 | 20 | 0/- | 100 | 2 | 4 | 15 | 0 | 16 | 1 | 633 | |
| -🇳🇱 | Defender | 1 | 2 | 0 | 1 | 0 | 16/4 | 200 | 4 | 4 | 10 | 0 | 11 | 1 | 602 |
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 |
|---|---|---|---|---|---|---|---|---|---|
| 30000 | 238 | 238Hz | 12 | 13 | 15 | 0 | Minor variation | ||
| 25000 | 400 | 280Hz | 12 | 14 | 16 | 0 | Minor variation | ||
| 30000 | 498 | 498Hz | 9 | 9 | 10 | 0 | Good connection | ||
| 30000 | - | - | 13 | 14 | 15 | 0 | Good connection |
Match feedback based on the player's usual level and their role in this game.
| Player | Verdict | Role | Performance Notes |
|---|---|---|---|
| Godlike | Attacker | Well played, this was a fantastic performance at 1.81x. Excellent flag running from you: 19 grabs became 6 caps and 5 solos. You did make some good returns, and those stops helped your team stay in the game. Next focus: keep attacking, but work with your teammates more and use cover effectively so your runs last longer. | |
| Godlike | Attacker | Great game, this was a really strong performance from you at 1.63x. You carried real threat on attack, turning 20 grabs into 5 caps and 2 solos. Aim was a real positive at 41% accuracy, so keep taking fights where that strength matters. Next focus: keep attacking, but work with your teammates more and use cover effectively so your runs last longer. | |
| Godlike | Attacker | You were one of the players who shaped this match, finishing at 1.45x. You were dangerous with the flag: 20 grabs led to 1 cap and 1 solo. Aim was a real positive at 41% accuracy, so keep taking fights where that strength matters. Next focus: turn pressure into cleaner outcomes by choosing the route before the flag leaves the stand. | |
| Struggling | Defender | You had a quieter game than normal at 0.79x; I think the useful part is that your improvement target is visible. You helped keep the score under control with 10 mid returns and 1 clutch return. You had some really good returns and gave useful cover, so keep building on that team-first work. Next focus: keep reading the incoming routes, but add more cover for your own returning carrier when the flag is safe. |