18 May 2026, 01:39
CTF-MountainCross
CTF-MountainCross
[IG+] ¯/_( ° >°)_/¯ - UH London Pug Server 1- pho`
iCTF
Duration 8:03
Red 0 : 0 Blue
CTF-MountainCross
18 May 2026, 01:39
CTF-MountainCross
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| tOLOzZFB | 2 | 2 | 0 | 0 | 4 | - | 2 | 100% | 50% | 0:24 |
| saxon | 0 | 0 | 0 | 0 | 38 | - | 0 | 0% | 61% | 0:24 |
| Team Total | 2 | 2 | 0 | 0 | 42 | - | 2 | 100% | 60% | 0:48 |
Red versus Blue balance for this match only.
Killer and victim pairings by team.
| Killer | Victim | |
|---|---|---|
| tOLOzZ | Broken_Soul | 1 |
| tOLOzZ | -uh.StarzZz`- | 1 |
| Killer | Victim | |
|---|---|---|
| No matchups recorded | ||
| Player | Double | Multi | Ultra | Monster | Ludicrous | Holy Shit | Best |
|---|---|---|---|---|---|---|---|
| tOLOzZ | 1 | 2 kills |
| Player | Killing Spree | Rampage | Dominating | Unstoppable | Godlike | Best |
|---|---|---|---|---|---|---|
| tOLOzZ | 2 kills |
Loading player feedback...
Generated from the match events and player statistics.
A tight game of 2v2 Instagib CTF took place on CTF-MountainCross between Red and Blue Team, ending 0-0 after both teams finished level.
Neither side recorded a capture, so the match was defined by pressure and recovery. Flag pressure remained limited across both teams.
tOLOzZ stood out as the main objective influence with 0 grabs, 0 captures, 0 returns, and an MVP score of 10.
saxon supplied the sharpest shooting numbers, finishing with 61% accuracy and 0 kills.
Banter read: tOLOzZ was the main CTF problem, turning useful moments into scoreboard paperwork.
Lama watch: tOLOzZ finished with 2 lama score from 2 kills and 0 objective actions, which is the stats page politely asking what the plan was.
The match ended without a clear winner, with both teams trading enough pressure to keep the result balanced.
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| - | tOLOzZ | Defender | 0 | 0 | 0 | 0 | 0 | 0/- | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 10 |
| - | saxon | Defender | 0 | 0 | 0 | 0 | 0 | 0/- | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
| Player | Score | Kills | Deaths | Suicides | Shots | 360 | K/D | Eff | Acc | TTL |
|---|---|---|---|---|---|---|---|---|---|---|
| Broken_Soul | 0 | 0 | 1 | 0 | 25 | 58.3 cm | 0.00 | 0% | 36% | 0:24 |
| -uh.StarzZz`- | 0 | 0 | 1 | 0 | 0 | 13.5 cm | 0.00 | 0% | 0% | 0:24 |
| Team Total | 0 | 0 | 2 | 0 | 25 | 35.9 cm | 0.00 | 0% | 36% | 0:48 |
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.
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 |
|---|---|---|---|---|---|---|---|---|---|
| saxon | 30000 | 600 | 500Hz | 10 | 10 | 10 | 0 | Limited ping data | |
| tOLOzZ | 30000 | - | - | 38 | 38 | 38 | 0 | Limited ping data | |
| Broken_Soul | 30000 | - | - | 23 | 23 | 23 | 0 | Limited ping data | |
| -uh.StarzZz`- | 30000 | 238 | 238Hz | 16 | 16 | 16 | 0 | Limited ping data |
Match feedback based on the player's usual level and their role in this game.
| Player | Verdict | Role | Performance Notes |
|---|---|---|---|
| tOLOzZ | Feeding | Defender | This was a hard outing for you at 0.16x; 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. Aim was a real positive at 50% accuracy, so keep taking fights where that strength matters. Next focus: when your base is secure, look for chances to help your carrier with cover on the way home. |
| saxon | Feeding | Defender | You had a rough game at 0.07x, so I think your goal should be to simplify and rebuild from safer plays. As a defender, you were involved, but earlier reads on incoming grabs and cleaner return positioning would lift your game. Aim was a real positive at 61% accuracy, so keep taking fights where that strength matters. Next focus: cover the flag carriers when you can, but make sure your own flag is safe first. |
| Broken_Soul | Feeding | Defender | You had a tough match at 0.03x, well below your usual level, but I think it is fixable. Your defensive shape was there in parts, but stronger first contact and faster return calls would raise your value. 0% efficiency points to too many low-value duels; wait for support or fight from stronger positions. Next focus: protect your own flag first, then help the carrier survive with cover when the chance is there. |
| -uh.StarzZz`- | Feeding | Defender | You had a tough match at 0.00x, well below your usual level, but I think it is fixable. Your defensive shape was there in parts, but stronger first contact and faster return calls would raise your value. 0% efficiency points to too many low-value duels; wait for support or fight from stronger positions. Next focus: when your base is secure, look for chances to help your carrier with cover on the way home. |
