The tracker turns live FiveM observations into comparable server, player and resource statistics. This page explains what each number means, where uncertainty remains and which claims FiveSearch deliberately avoids.
Server IDs and observed connected-client counts come from the live FiveM network. FiveSearch refreshes the parsed list continuously. A temporary upstream or database outage is shown as delayed data rather than a new zero value.
Resource names, player lists and technical fields come from a rate-limited single-server endpoint. A background crawler scans servers over time, so resource coverage is a sampled subset and is not simultaneous across every server.
Country and region statistics use the locale reported by each server. They do not prove the physical location of the machine or the location of its players, and they are not a latency measurement.
Where available, FiveSearch compares a server's self-reported client value with the count visible in the live network. Timing differences can occur, so network-level comparison results are indicators rather than accusations about an individual operator.
An installation means a technical resource identifier was observed on a scanned server. It does not prove authorship, licensing, version, configuration or a dependency relationship. Adoption claims must state scan coverage and observation time.
Each server's published address is mapped to its network with local datasets: a public routing dataset for the network and its operator, and IP Geolocation by DB-IP (CC BY 4.0) for the country. Operators are grouped into datacenters, DDoS filters and home connections by their network names and numbers; a network no rule names counts as a datacenter once three or more listed servers share one of its /24 blocks, because hosts rent out neighbouring addresses while home connections are scattered. A filter's address shows the filter, never the machine behind it.
Addresses of home connections are shortened to their network and never listed. Once a server moves behind a DDoS filter, its earlier direct addresses are hidden, because they would point past the filter. Servers that keep their address private in the live network are counted as such and never looked up.
The product can contain more servers and resources than the search index. FiveSearch only submits detail pages that meet current activity, history and data-quality thresholds; the rest can remain available inside the tracker without being promoted to search engines.
Server owners and resource maintainers can document a correction through oxince. Include the tracker URL, the field in question and a verifiable source. Public observations are corrected at the data or classification layer; historical measurements are not silently rewritten. Owners can also ask for their owner profile to be removed from the tracker.