Unreal HeavenThe home of 2v2 and 3v3 iCTF3 Aug 2025, 23:05
CTF-Bolt_HE (s0urCe edit for UH)
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| ownage | 121 | 42 | 15 | 0 | 160 | - | 2.80 | 74% | 46% | 0:49 |
| newutFB | 62 | 16 | 11 | 0 | 39 | - | 1.45 | 59% | 44% | 0:18 |
Red versus Blue balance for this match only.
Killer and victim pairings by team.
| Player | Double | Multi | Ultra | Monster | Ludicrous | Holy Shit | Best |
|---|---|---|---|---|---|---|---|
| ownage | 6 | 2 | 2 | 5 kills | |||
| localhero | |||||||
| newut | 2 | 1 | 3 kills |
Loading player feedback...
Generated from the match events and player statistics.
A decisive game of 3v3 Instagib CTF took place on CTF-Bolt_vS0urCe between Red and Blue Team, ending 4-0 in favour of Red Team.
The opening breakthrough came at 0:35 when Maber scored for Red Team. Red Team created more scoring chances, converting 4 of the 4 captures. The scoring pattern stayed relatively stable once the first lead was established. 2 captures were completed solo.
The final capture arrived at 2:29, with newut finishing for Red Team on a solo run. That score set the closing shape of the match at 4-0.
newut stood out as the main objective influence with 2 grabs, 2 captures, 0 returns, and an MVP score of 255. ownage anchored the recovery work with 4 total returns.
Objective ledger for the match: 12 grabs, 5 pickups, 4 captures, 2 solos, 2 assists, 12 flag kills, 13 covers, 11 seals, 7 returns, 0 mid returns, 0 clutch returns, and 0 cherry picks.
ownage supplied the sharpest shooting numbers, finishing with 46% accuracy and 42 kills.
Banter read: newut was the main CTF problem, turning useful moments into scoreboard paperwork.
Lama watch: localhero finished with 5 lama score from 11 kills and 3 objective actions, which is the stats page politely asking what the plan was.
Red Team ultimately secured the result through stronger capture conversion and late-game control.
| 37 |
| 5 |
| 13 |
| 0 |
| 26 |
| - |
| 0.38 |
| 28% |
| 19% |
| 0:15 |
| Team Total | 220 | 63 | 39 | 0 | 225 | - | 1.62 | 62% | 43% | 1:24 |
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| -uh.StarzZz`- | 39 | 15 | 27 | 0 | 42 | 13.5 cm | 0.56 | 36% | 36% | 0:56 |
| localhero | 19 | 11 | 12 | 0 | 42 | - | 0.92 | 48% | 26% | 0:14 |
| _-=Pr3dazZz=- | 13 | 13 | 24 | 0 | 118 | 36.0 cm | 0.54 | 35% | 21% | 0:26 |
| Team Total | 71 | 39 | 63 | 0 | 202 | 24.7 cm | 0.62 | 38% | 27% | 1:38 |
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.
| Player | Killing Spree | Rampage | Dominating | Unstoppable | Godlike | Best |
|---|
| ownage | 3 | 1 | 10 kills | |||
| localhero | 1 | 5 kills | ||||
| newut | 3 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| - | newut | Defender | 2 | 2 | 1 | 1 | 0 | 0/- | 205 | 2 | 4 | 0 | 0 | 0 | 0 | 255 |
| - | Maber | Attacker | 5 | 2 | 1 | 1 | 1 | 0/- | 195 | 1 | 0 | 0 | 0 | 1 | 0 | 215 |
| - | ownage | Defender | 0 | 0 | 0 | 0 | 0 | 6/6 | 0 | 0 | 7 | 0 | 0 | 4 | 0 | 170 |
| - | -uh.StarzZz`- | Defender | 2 | 0 | 0 | 0 | 0 | 4/2 | 0 | 1 | 2 | 0 | 0 | 1 | 0 | 41 |
| - | localhero | Defender | 0 | 0 | 0 | 0 | 0 | 1/- | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 15 |
| - | _-=Pr3dazZz=- | Defender | 3 | 0 | 0 | 0 | 0 | 0/- | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 13 |
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 |
|---|---|---|---|---|---|---|---|---|---|
| Maber | 25000 | 295 | 143Hz | 35 | 36 | 39 | 0 | Minor variation | |
| ownage | 30000 | - | - | 106 | 108 | 111 | 0 | Good connection | |
| newut | 30000 | 0 | 240Hz | 93 | 96 | 101 | 0 | Minor variation | |
| -uh.StarzZz`- | 30000 | 238 | 238Hz | 13 | 14 | 14 | 0 | Good connection | |
| _-=Pr3dazZz=- | 30000 | 498 | 498Hz | 11 | 11 | 12 | 0 | Good connection | |
| localhero | 30000 | - | - | 21 | 35 | 101 | 1 | Occasional lag spikes |
Match feedback based on the player's usual level and their role in this game.
| Player | Verdict | Role | Performance Notes |
|---|---|---|---|
| Maber | Stable | Attacker | I think you had a steady game at 1.02x; one or two stronger moments would lift it nicely. You ran the flag well and gave your team end product: 2 caps and 1 solo from 5 grabs. 28% efficiency points to too many low-value duels; wait for support or fight from stronger positions. Next focus: turn pressure into cleaner outcomes by choosing the route before the flag leaves the stand. |
| newut | Struggling | Defender | You dipped below your usual level at 0.85x, but I think there are clear areas you can tighten next match. Your defensive shape was there in parts, but stronger first contact and faster return calls would raise your value. Aim was a real positive at 44% accuracy, so keep taking fights where that strength matters. Next focus: protect your own flag first, then help the carrier survive with cover when the chance is there. |
| ownage | Struggling | Defender | You dipped below your usual level at 0.84x, but I think there are clear areas you can tighten next match. Your defensive shape was there in parts, but stronger first contact and faster return calls would raise your value. You fought efficiently: 42-15 with a 2.80 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. |
| -uh.StarzZz`- | Feeding | Defender | This was a hard outing for you at 0.32x; treat it as a reset point, not a verdict on your ability. You had defensive involvement, but your next step is being first to the danger more often, not just reacting after the grab. 36% efficiency points to too many low-value duels; wait for support or fight from stronger positions. Next focus: after the flag kill, secure the return faster or call the exact location so the team can finish the stop. |
| localhero | Feeding | Defender | You had a rough game at 0.25x, so I think your goal should be to simplify and rebuild from safer plays. You had defensive involvement, but your next step is being first to the danger more often, not just reacting after the grab. You had a mixed game rather than a specialist one; adding one clear strength, such as safer returns or better cover timing, would make your impact easier to see. Next focus: after the flag kill, secure the return faster or call the exact location so the team can finish the stop. |
| _-=Pr3dazZz=- | Feeding | Defender | You had a rough game at 0.15x, so I think your goal should be to simplify and rebuild from safer plays. You had defensive involvement, but your next step is being first to the danger more often, not just reacting after the grab. 35% efficiency points to too many low-value duels; wait for support or fight from stronger positions. Next focus: keep reading the incoming routes, but add more cover for your own returning carrier when the flag is safe. |