Skip to content

QBCore server count

How many public servers report qb-core? This report publishes the latest completed count from qbcore.net's daily scan of the FiveM server list, with the observation window and coverage needed to interpret it.

Latest completed scan

5,086 public servers reporting qb-core

Observation started
Scan completed
Listed entries
33,490
Inspected entries
29,625
Resource lists visible
29,618

Resource-data coverage: 88.4% of listed entries. This measures visibility of resource data, not framework market share.

Counting method · History · What the count means · Cite this observation

Counting method

  1. Read Cfx.re's public server-list feed and deduplicate entries by their server join ID.
  2. Inspect public resource data. When the feed omits it, check the server's public detail record. Exclude records identified as RedM rather than FiveM.
  3. Count a server once when its resource list includes the exact name qb-core. The server name, tags, a qb- prefix, or qbx_core alone do not qualify. A listed server with zero players can still count.
  4. Publish the aggregate after the full scan completes. An interrupted scan does not replace the last successful result with a partial count.

The resource name comes from the upstream qb-core repository. Detecting that name does not verify the deployed code, its version, or whether it is an unmodified upstream installation.

Read the observation window and coverage

The start time records when the source listing was obtained. The completion time records when inspection finished. Individual servers are inspected at different points in that window, so the result is not a simultaneous online-server total.

Scans are scheduled approximately daily and can take hours. After a failure, the previous count keeps its original dates. A refresh-delay notice appears when the observation began more than 72 hours ago. The report can briefly lag a completed scan while its cached page refreshes.

What the count means

This is an observed minimum of public servers advertising qb-core. It does not include every QBCore installation. Unlisted or private servers, hidden or renamed resources, and records unavailable during inspection cannot be identified by this method.

The count does not measure unique server owners, communities, players, downloads, server quality, or framework market share. Resource visibility varies, and a detected name alone cannot establish compatibility or authenticity.

Historical observations are retained starting with the deployment of the history feature. Older unrecorded scans cannot be reconstructed from the current snapshot. A changed count can reflect source-list availability or visibility as well as changes in server usage. Only compare scans with their coverage denominators and observation windows; a count difference does not establish framework adoption growth or decline.

Completed scan history

Up to 30 recent completed observations. Dates refer to collection windows; the line joins separate scans, not continuously observed usage. A changing count can reflect listing and resource-data coverage, not just changes in server usage.

Observed public qb-core countsCounts range from 5,086 to 5,930 in the displayed scan windows. See the table for exact observations and coverage.
Completed public resource-list scans, oldest to newest
Scan started (UTC)Observed qb-coreResource visibility
5,53528,584 / 34,801
5,92430,939 / 35,268
5,93031,102 / 35,613
5,50929,005 / 35,322
5,79330,794 / 35,160
5,76330,784 / 35,169
5,48729,419 / 35,176
5,67630,849 / 35,147
5,46329,727 / 35,579
5,69531,184 / 35,667
5,58230,860 / 35,152
5,59030,885 / 35,048
5,36530,169 / 34,339
5,35430,044 / 34,103
5,18129,024 / 34,351
5,40930,574 / 34,828
5,36730,703 / 35,053
5,26730,296 / 34,424
5,10829,382 / 34,288
5,22230,090 / 34,062
5,11829,752 / 33,636
5,08629,618 / 33,490

Export validated aggregates as JSON history. Historical data begin when retention is enabled, not at the first-ever server count.

The read-only JSON history endpoint exposes aggregate counts and coverage only, without server IDs, individual listings, or private data. A usable trend appears once multiple completed scans have been retained. Failed or interrupted scans are never shown as measured zero. You may cite this URL with observation dates, but do not call these data framework market share.

Cite this observation

Use the count together with its observation window and coverage. The wording below keeps those limits attached when you reference the result.

qbcore.net observed 5,086 public servers advertising the exact resource name qb-core during a scan from 20 Nov 2026, 16:42 UTC to 20 Nov 2026, 21:37 UTC. Resource lists were visible for 29,618 of 33,490 listed entries. This is an observed minimum, not all QBCore installations or market share. Source: https://qbcore.net/qbcore-server-count

This URL always shows the latest available result. Save the quoted observation and its dates with your work if you need to retain a particular snapshot. The Markdown version contains the methodology; read this report for the dated count.

About this report

qbcore.net produces this aggregate from public Cfx.re server data. It is an independent community report, not a statistic published or endorsed by the QBCore project or Cfx.re. See About QBCore.net for the maintainer and contact details, or report an error with the observation dates and the issue you found.

For implementation details on your own server, start with the qb-core resource guide or the QBCore installation guides.