# 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](https://servers.fivem.net/), with the observation window and coverage needed to interpret it.

[Counting method](#counting-method) · [History](#completed-scan-history) · [What the count means](#what-the-count-means) · [Cite this observation](#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](https://github.com/qbcore-fivem/qb-core). 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.

- **Listed entries:** unique server IDs in the source feed, before game and resource-visibility checks.
- **Inspected entries:** records available for inspection after the initial game filter. Entries that disappear before inspection may be absent here.
- **Resource lists visible:** inspected FiveM entries with a usable public resource list. The QBCore count comes from this group.
- **Resource-data coverage:** visible resource lists divided by all listed entries. This describes the scan's visibility, not QBCore's market share.

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

The [read-only JSON history endpoint](/api/v1/server-count-history) 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.

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](/qbcore-server-count.md) 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](/about) for the maintainer and contact details, or [report an error](/support#report-a-documentation-error) with the observation dates and the issue you found.

For implementation details on your own server, start with the [qb-core resource guide](/docs/resources/qb-core) or the [QBCore installation guides](/docs/installation).
