Loading match report…
Ban status is PUBG's own verdict from the official API. We only know about accounts our sweep has already checked, so treat this as a floor rather than a full audit — and a ban can be issued long after the match was played.
| # | Operator | Kills | Damage | Survived |
|---|---|---|---|---|
| 1 | Gabelo01 | 4 | 366 | 3:34 |
| 1 | SirSmokey12 | 3 | 282 | 3:34 |
| 1 | Ratahtat | 2 | 202 | 3:34 |
| 1 | TruLeonidas | 1 | 169 | 3:34 |
| 2 | AZZKIKR_OG | 3 | 255 | 3:30 |
| 2 | fRiks | 0 | 55 | 2:07 |
| 2 | fucJUMPSTREET | 0 | 0 | 3:30 |
| 2 | Onvi06Temp ban | 0 | 110 | 3:30 |
| 3 | Pachekof25 | 0 | 164 | 2:00 |
| 3 | PeligroPower | 0 | 44 | 1:38 |
| 3 | VIKKINGO77 | 0 | 97 | 1:39 |
| 4 | Chewy312 | 0 | 100 | 1:39 |
| 4 | Magehammer | 0 | 62 | 0:42 |
| 4 | Sausage1 | 0 | 119 | 1:39 |
| 4 | XFXnovablink | 0 | 0 | 1:27 |
| 5 | Stark_0429 | 0 | 0 | 1:03 |
| 5 | Surprise_M-F | 0 | 0 | 1:07 |
Archived from PUBG match telemetry · match id a7628270-a59b-4b30-ba19-cd8438e34b0e