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 | Jiew4 | 3 | 344 | 6:58 |
| 1 | Hoa_Hoc_11 | 2 | 164 | 6:58 |
| 1 | zzzyyyan | 2 | 245 | 6:58 |
| 1 | 4AMSimpleing | 0 | 211 | 6:58 |
| 2 | Ercy- | 2 | 812 | 6:55 |
| 2 | ky9999999 | 0 | 0 | 2:11 |
| 3 | sunfire97 | 2 | 30 | 6:04 |
| 3 | HMT-XXITemp ban | 1 | 334 | 6:34 |
| 3 | zhenshenling | 1 | 137 | 6:34 |
| 3 | CuCaiBietBay | 0 | 20 | 6:34 |
| 4 | z0401144 | 1 | 144 | 3:27 |
| 4 | GB_QuocHuy | 0 | 76 | 3:30 |
| 5 | AKA_ZGG01 | 0 | 101 | 3:18 |
| 5 | Lzls | 0 | 100 | 1:19 |
| 5 | NgTu9x | 0 | 0 | 1:01 |
| 5 | SatrixPlatinum | 0 | 0 | 1:53 |
| 5 | z99000l | 0 | 77 | 1:19 |
| 6 | jywx- | 0 | 0 | 0:34 |
Archived from PUBG match telemetry · match id ff7f6da5-6a6d-4a6d-aa2b-f253d2c1338a