01 / Start here
Choose the problem you want to solve
Turn a match identifier into a defensible replay question. Start with the correct platform and account, follow resource relationships to the match asset, then interpret a short event sequence before building totals or drawing routes. This site is for people inspecting PUBG API data, not a live stats service. Tokens stay in your private environment. The linked developer documentation supplies field definitions; examples below are illustrative and do not impersonate a fetched player match.
01Resolve the supported platform shard and account, fetch an available match and follow its related telemetry asset URL. Index included resources by type and ID instead of counting them as players. Preserve match metadata separately from telemetry so a failed download can be retried without repeating every lookup.
Full steps and alternatives ↗
02Define the question and event scope before summing. Inspect event type, timestamp, actor and victim; keep absent actors absent. Damage, knock and elimination answer different questions, and later event versions can require different interpretation. Validate a short ordered sequence against the official definitions before aggregating a whole match.
Full steps and alternatives ↗
03Confirm map identity, dimensions, axis direction and coordinate units before drawing. Validate several known positions against the chosen image and preserve gaps in the event stream. A line between recorded positions is an interpolation, not proof of the route a player traveled.
Full steps and alternatives ↗
04Separate API availability from analysis failure. Confirm shard, identifiers, response status and documented availability before declaring data lost. Use official samples to validate parsing without relying on one player's match. Check known issues and versioned event definitions before interpreting an absent field as a player action.
Full steps and alternatives ↗