Observed Weapon Telemetry
Measured sample joined to active verified weapon identities
Inspect raw player-match weapon observations, mapped weapon kills, damaging events, and their exact match and participant denominators.
View measured weapon data →
PUBG Data & Analysis
Each page states its source, sample, and coverage. Measured telemetry, verified catalog fields, level groupings, and editorial references are kept clearly separate.
Current data coverage
MEASURED
Verified Weapon Data Viewer
Verified active-build constants
Filter and chart verified base damage, initial speed, and cycle cadence (60 ÷ exact fire interval). No damage outcomes are calculated.
Open the verified catalog →
Current data coverage
W
Observed Weapon Tiers
The automatic S+–F view orders active verified weapons by observed catalog-mapped kills in a rolling seven-day telemetry sample.
- Exact match, participant, and mapped-kill sample
- Observed sample ranking—not a controlled weapon-power grade
View observed weapon tiers →
A
Armor Level Groups
Helmets and vests are grouped only by the equipment level in the active selectable catalog.
- Verified catalog identity and equipment level
- No unverified durability or reduction values
View armor level groups →
T
Observed Throwable Tiers
Throwables are ordered by exact observed use events and use share for the selected telemetry window.
- Raw observed use counts and shares
- Explicit loading, empty, and unavailable states
View observed throwable tiers →
V
Observed Vehicle Tiers
Vehicles are grouped by exact vehicleId and vehicleType values and ranked by retained LogVehicleRide event count and share. This is event frequency, not unique vehicle usage or performance.
- Exact LogVehicleRide counts and shares by vehicleId and vehicleType
- Observed event frequency—not unique vehicles, speed, durability, or utility
View observed vehicle tiers →
How to interpret these pages
A high observed count shows what appeared in this collected sample; it does not by itself prove that an item is intrinsically stronger. Every page must name the value it ranks and keep unavailable source fields blank.
- Measured rates always name and expose their numerator and denominator.
- Verified catalog values are limited to the accepted current-build source subset.
- Editorial or level-based groupings are never labeled as measured performance.
Related data pages
Attachment Meta
Observed attachment equip events
Balance History
Patch stat changes timeline
Weapons
Browse active verified weapon identities and source-backed current-build fields.