When does the server hitch?
Server-thread time and every hitch warning, with a Discord alert when it starts.
The resource reads server-thread time and hitch warnings, connection failures, queue length (in deep mode), jobs on duty, cash and bank supply, txAdmin whitelist progress and store purchases.
See when the server thread hitches, how long the queue gets, whether EMS is covered tonight and what priority queue earns.
Free for one server. No card needed.
What the demo dashboard answers for this game.
Server-thread time and every hitch warning, with a Discord alert when it starts.
Queue length at peak (with serverstats_deep on) and how many connections fail, by stage.
Police, EMS and mechanics on duty by hour, and what happens when EMS runs thin.
Cash and bank supply, and where money comes from and where it goes.
Tebex revenue by package, matched to players when you set serverstats_id_type to fivem.
From txAdmin application to approval to first session, and how waiting time changes it.
One server resource. There's no client script, and nothing is sent to players' games.
/perf/ endpointserverstats_deep on)serverstats_id_type fivem (Operator)No install yet? Basic mode reads /dynamic.json and /info.json over HTTP on port 30120. Check any FiveM server with the FiveM server status checker.
A dashboard shaped like your server, and a log of who paid whom.
We suggest the gamemode from the plugins we detect, and you confirm it. Anything else gets the general dashboard. Race and drift stats are next.
Every payment, trade, shop sale and punishment in one log you can filter by player. Abuse flags point out large transfers, alt-account funnels, transfer rings and staff paying themselves.
FiveM money logs for ESX, QBCore and Qbox · Spotting alt funnels and staff abuse · Plans · Privacy
FXServer runs every resource's server scripts on its main thread. When a tick takes too long, the server prints a hitch warning, and players feel it as desync and delayed actions. ServerStats reads the tick-time histograms for the main, sync and network threads from FXServer's own /perf/ endpoint, the way txAdmin does, and counts every hitch warning per thread.
What it doesn't do is name the resource. FXServer only exposes per-resource CPU through its profiler console commands, which cost CPU while they record. Use ServerStats to see when hitches happen and what else was going on (players, entities, a resource restart), then record a profile at that time. The resource CPU guide walks through it.
If /perf/ can't be read, the resource falls back to its own Lua frame times and serverstats status says so.
Works with
# Put the serverstats resource in resources/, then: set serverstats_claim "SS-XXXX-XXXX-XXXX" ensure serverstats
FXServer's main thread fell behind by the number of milliseconds in the message. One now and then is normal; a stream of them at peak means the server can't keep up. ServerStats counts them per thread and can alert you in Discord when they start.
Yes. The FiveM Incidents page places drops and resource starts or stops in the same time buckets, then shows their exact timestamps in a log. It also breaks down drop reasons and connection failure stages. Events close together are a lead to investigate, not proof that the resource caused the drops.
Not directly: FXServer only gives per-resource CPU through its profiler commands. ServerStats tells you when the server thread slows and hitches, next to players, entities and resource restarts, so you know when to record a profile and what to compare it with.
Qbox, QBCore, ESX Legacy and ND_Core are detected automatically, plus ox_inventory, txAdmin and the banking resources listed above. vRP is in beta and gives money flows, not player-to-player payments. Standalone servers get everything except framework-specific economy and job data.
Very little. The collectors are small counter updates on the server thread, uploads are batched, and gzip runs off the thread. serverstats status shows the resource's own server-thread cost per tick.
Analytics use a keyed hash of each license. The original is kept encrypted with your account's key so you can look players up and moderate them, and it's never shown in the dashboard. IPs, tokens and HWIDs never reach us.
Yes. It reads txAdmin's events for kicks, warns, bans, whitelist requests and scheduled restarts. Reasons and announcement text are never read.
Free covers one server with 24 hours of history, forever, with no card. Operator is $9.99 a month for 10 servers and 90 days of history, which you need for week-on-week trends and D7 or D30 retention. Yearly billing gives two months free.
One ServerStats account covers every game you run.