FiveM analytics for hitches, drops and queues.

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.

Questions it answers for FiveM servers

What the demo dashboard answers for this game.

When does the server hitch?

Server-thread time and every hitch warning, with a Discord alert when it starts.

How long is the queue, and who leaves it?

Queue length at peak (with serverstats_deep on) and how many connections fail, by stage.

Are my jobs covered?

Police, EMS and mechanics on duty by hour, and what happens when EMS runs thin.

Is the economy balanced?

Cash and bank supply, and where money comes from and where it goes.

Does priority queue sell?

Tebex revenue by package, matched to players when you set serverstats_id_type to fivem.

Do whitelist applicants play?

From txAdmin application to approval to first session, and how waiting time changes it.

What ServerStats tracks on FiveM servers

One server resource. There's no client script, and nothing is sent to players' games.

Server health

  • Main, sync and network thread tick times, read from FXServer's own /perf/ endpoint
  • Hitch warnings and hitch length per thread
  • Entities by type, created and removed; resources started and stopped
  • Incidents view: player drops beside resource starts and stops, with a timestamped event sequence
  • OneSync explosions, and bursts of more than 10 from one player in 10 seconds

Players and queue

  • Players, slots used, connect attempts, connect time
  • Connection failures by stage, drop reasons (timeout, crash, kicked, banned)
  • Queue length (with serverstats_deep on)
  • Ping, sessions, D1, D7 and D30 retention

Roleplay

  • Characters loaded, jobs and players on duty by job, duty minutes
  • Gang changes, jailings, revives and deaths
  • txAdmin kicks, warns, bans, whitelist requests and scheduled restarts

Economy and store

  • Cash and bank supply among online characters
  • Money added and removed by reason, transactions over 100,000
  • Vehicle purchases, fines, bills and hospital respawns (qb jobs)
  • ox_inventory shop sales, crafts and items used
  • Tebex revenue by package, matched to players with 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.

FiveM gamemodes, payments and punishments

A dashboard shaped like your server, and a log of who paid whom.

Dashboards per gamemode

  • Serious RP (whitelisted)
  • Semi-serious / economy RP
  • PvP / combat

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.

Logs and flags

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.

What we listen to You pick the plugin for each area

Payments and money
QboxQBCoreESX LegacyND_CorevRP beta (money in and out only, no player-to-player payments)
Banking
qb-bankingRenewed-Bankingpefclesx_banking
Items and shops
ox_inventory (gives and shop sales)
Jobs and paychecks
QboxQBCoreESX LegacyND_CorevRP beta
Vehicles and property
qb- and qbx_vehicleshopesx_vehicleshopqb-housesqbx_propertiesps-housingesx_property
Police, fines and bills
qb-policejobqbx_policeesx_policejobesx_billing
Gangs and societies
QBCore and Qbox gangsesx_addonaccount
Punishments
txAdmin

The number that matters: server-thread time and hitches

svMain
FXServer's main server thread, where server scripts run
Threads timed
svMain, svSync, svNetwork
Source
FXServer /perf/
Hitch warnings
Every one, per thread
Per-resource CPU
Not measured

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.

One resource. About five minutes.

Works with

  • FXServer
  • OneSync
  • Qbox
  • QBCore
  • ESX
  • ox_inventory
  • txAdmin
  • Tebex
  • Connects out only. No ports to open on your server.
  • A one-time claim code, then the agent signs everything it sends with its own key. No reusable secret is stored on your server or ours.
  • Player IDs are keyed hashes in analytics. Player IP addresses are never sent to us.
server.cfg
# Put the serverstats resource in resources/, then:
set serverstats_claim "SS-XXXX-XXXX-XXXX"
ensure serverstats

FiveM questions

What does a “server thread hitch warning” mean?

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.

Can I see whether a resource restart preceded player drops?

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.

Can ServerStats tell me which resource is causing lag?

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.

Which frameworks do you support?

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.

Will it add resmon load?

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.

Do you store player licenses or IPs?

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.

Does it work with txAdmin?

Yes. It reads txAdmin's events for kicks, warns, bans, whitelist requests and scheduled restarts. Reasons and announcement text are never read.

Is it free?

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.

Related games

One ServerStats account covers every game you run.

Start with one FiveM server, free

Install it and see your first numbers today.