Trust starts with a source.
Different tools use different kinds of evidence. Here is what is bundled, and what is calculated.
Player statistics
This site has no live lookup: the PUBG Developer API needs a private key, and a static site has nowhere to keep one. The match tools read only the file you import, in your browser. Imported records and examples are labeled separately.
Source / reference ↗Weapon reference
The imported game-file extraction is dated 2026-10-28. Game-file values can include event variants and do not establish current competitive weapon strength. Ballistic limit is not effective range.
Maps & coordinate layers
Official 8,192-pixel artwork uses a pinned October 2024 source. Coordinates come from a newer community extraction with its own date and map extent. Spawn candidates are not guaranteed spawns; newer terrain may not match the older artwork.
Source / reference ↗Calculator & recommendations
Damage outputs use the displayed training assumptions. Range penalties, bone estimates, loadout fit scores, landing contest scores, and route detours are heuristics. They are not live game simulation, observed contest probabilities, or an AI prediction.
Open related tool →Research & learning
The connected experience draws on player lookup and ranking workflows from community tools, replay-oriented reviews in PUBG Stats Tracker, community questions on Reddit, creator demonstrations, and official patch/API documentation.