Scope of the sample

HHHEATMAP is built mainly from actual Steam Ranked matches associated with tracked high-tier leaderboard players, professional players and streamers. It is not a census of every PUBG player or every Ranked match.

Analysis happens in a separate local environment. The public site and a visitor's browser do not call the PUBG API or analyze telemetry. They only read processed coordinates and summaries that have already been analyzed, reviewed and stored.

Circle data: shared match observations

A circle belongs to the match rather than to one player. Time-series safe-zone states are examined in match telemetry, and a center coordinate and radius are extracted for each identified phase.

The same match can be encountered while analyzing different players. Match and phase identifiers are therefore used to prevent one circle from being accumulated repeatedly. The public heatmap transforms the resulting PUBG world coordinates into the coordinate space of each map image and overlaps observations from many matches.

Kill spots: the killer's position

Kill data is player-specific. Only events in which the killer account matches the tracked player are included, and the coordinate is where that player was standing when the kill occurred. It is not the victim's death location.

Events classified as suicides are excluded. If a player records several kills in one match, each event may contribute a separate coordinate. Processing history and record identifiers are used to avoid saving the same tracked player's match records repeatedly.

Separation by season, map and phase

Each match is associated with its collection-season label and map. Changing the public season limits match totals and both types of coordinates to that season. New-season data is accumulated separately instead of replacing historical seasons.

PUBG world coordinates are transformed for each map because map sizes and playable image bounds differ. Circles can be inspected by phase, and a kill location can be assigned to the match phase at the time of the event when that information is available.

Aggregation and presentation

Heat colors are normalized to show relative overlap within the current selection. A color alone cannot be converted back into an exact probability or raw count, and colors from maps or seasons with different sample sizes should not be treated as one absolute scale.

The season-card “Kill spots” figure counts distinct matches that contain at least one kill-location record. It does not count every kill coordinate, so this summary can differ substantially from the number of points used to render the layer.

Sample and data limitations

  • The tracked-player sample can emphasize the play styles of high-tier and professional players.
  • Match volume differs by season, map and phase; later phases generally contain fewer observations.
  • Game updates, telemetry formats, collection timing and source-data quality can cause omissions or classification errors.
  • The heatmap describes past observations and does not guarantee the next circle, match result or safety of a location.

If you find a clear coordinate or presentation error, use the Discord contact listed on the About & contact page.