Small, steady spreads beat one-off jumps this week

This week’s telemetry shows more of the same slow, selective churn: 1,620,072 distinct resource names were observed across FiveM servers, up from 1,601,275 a week earlier. That raw increase masks the real takeaway — adoption that looks like spread, not noise, is rare. Our 5+ days growth filter produced ten names this week; when a resource grows on most days it is behaving like an independently propagating dependency, not a one-off bundle. The roster of sustained growers this week mixes small-framework modules (qbx_core, qbx_vehicles, qbx_management) with map/interior packages from tstudio and a handful of prompt/rail assets (prompt_sandy_traintunnel, prompt_trainstation_paleto). Two items deserve particular attention for how they moved in percentage terms: tstudio_cayo_tunnel and energy_palazzoranch both started from very small bases and surged, which is exactly the pattern you get when a new interior or location is picked up by multiple servers in quick succession. By contrast, the qbx packages added servers slowly but consistently — the textbook sign of gradual adoption across many independent servers. On the down side, a number of widely used utilities ticked lower by a few dozen servers each; that sort of fluctuation is common and, in most cases, does not indicate a failure. In short: the week was defined less by a single breakout and more by scattered steady gains, and importantly, no prominent script vanished completely this week.

Sustained adoption is the story this week; ten resources grew on at least five of the seven measured days. tstudio_cayo_tunnel grew on 6/6 days — it is reported on 133 servers (prev week 9), a net +123 (+1307.9%), with daily counts 83→100→126→141→147→161→171. That pattern — single-digit starts then repeated gains across the week — looks like a new map or interior being picked up by multiple servers rather than a single large bundle. tstudio_lacima_estate also expanded on 6/6 days to 279 servers (prev week 190), +90 (+47.3%), daily 214→230→265→285→292→313→356; its steady climb resembles organic spread across many hosts. The qbx family showed quiet, broad growth: qbx_core is on 5,160 servers (prev week 5,069), +91 (+1.8%), daily 5118→5126→5131→5148→5152→5207→5236, and qbx_vehicles reached 5,020 (prev week 4,927), +93 (+1.9%), daily 4976→4992→5002→5010→5010→5058→5089. Both qbx_core and qbx_vehicles added servers on most days, a profile consistent with a dependency rolling out across independent communities rather than a single large install. qbx_management mirrors that behaviour: 4,436 servers (prev week 4,358), +78 (+1.8%), daily 4400→4413→4414→4425→4426→4470→4502. Vehicle- and studio-oriented packages also climbed: jg-vehiclestudio rose to 423 servers (prev week 336), +87 (+25.7%), daily 391→404→409→424→434→445→454, showing steady gains every day. Ultra-voltlab added 86 servers to reach 5,960 (prev week 5,873), +1.5%, daily 5911→5924→5938→5960→5955→5999→6029; its small, regular increases fit the slow-adoption pattern. Prompt-based train assets continued spreading: prompt_trainstation_paleto is at 348 (prev week 265), +83 (+31.2%), daily 324→335→342→350→354→366→363, and prompt_sandy_traintunnel reached 349 (prev week 262), +88 (+33.5%), daily 320→332→344→356→359→369→365 — both grew on five of six measured days and have the multi-day shape we treat as meaningful. Finally, moved to 84 servers (prev week 10), +74 (+749.4%), daily 37→56→78→93→102→109→113; like , it began from a small base and accumulated many installs quickly, which merits a check next week to see if the rise sustains or was driven by a few coordinated installs.

Downward movement this week is modest and shallow for most widely used modules. screenshot-basic fell by 95 servers to 16,252 (prev week 16,347), with daily 16292→16295→16246→16249→16159→16238→16284; that’s a small percentage wobble on a very large base and doesn’t look like a collapse. PolyZone lost 77 servers to 17,556 (prev week 17,633), daily 17594→17563→17554→17569→17486→17526→17597, another tiny change relative to scale. Several qb-* modules recorded low single- or two-digit percentage declines: qb-weathersync is at 5,214 (prev week 5,299), -84 (-1.6%), daily 5252→5224→5203→5223→5182→5199→5215; qb-management and qb-spawn dropped 64 each, to 6,115 and 4,004 respectively. okokNotify and okokBilling together lost 153 installs across the week — okokNotify at 3,691 (prev week 3,779) and okokBilling at 2,279 (prev week 2,345) — but neither shows the straight-line disappearance that would indicate widespread breakage or deprecation. Generic utility modules such as generic_texture_renderer_gfx and qb-minigames also ticked down by a few dozen servers each. No prominent script vanished completely this week. The declines are real but modest: they merit attention only if they continue next week or coincide with public notices from authors; otherwise they read as routine churn on large installed bases.

This week produced several new resource names that reached non-trivial counts in their first seven days. cfx-gomstyling-subpack-12 was first seen 2026-07-01 and reached 43 servers; 204sRuiner (first seen 2026-07-02) reached 40 servers; and tstudio_poledance (first seen 2026-07-04) reached 39 servers. A cluster of new “_text” entries — zalandosans_text, montserrat_text, fredoka_text, monoton_text, luckiestguy_text, college_text and cinzel_text (first seen between 2026-06-29 and 2026-07-01) each reached 34–35 servers. Font and text-pack names often come from theme or UI bundles and can reflect either a shared asset pack or multiple servers adopting the same visual asset; their uniform sizing suggests a common origin or one pack that was copied across a few servers. The handful of new packages that cleared the 30–40 server threshold are worth a second look: they have exceeded the ‘one private-server’ noise floor and could be nascent community packages or small collections that will either continue to spread slowly or stabilize at these counts.

For developers and server operators the two practical signals to follow next week are pattern and persistence. A resource that added tens of servers in a single day and then stalls is different from one that grows on 5–6 days; the latter (qbx_core, qbx_vehicles, qbx_management, prompt_trainstation_paleto, prompt_sandy_traintunnel, jg-vehiclestudio) is where you should prioritize compatibility checks and documentation. The two high-percentage risers from small bases (tstudio_cayo_tunnel and energy_palazzoranch) deserve monitoring: if they continue to add servers across the next week they have crossed the ‘noticed by other operators’ threshold; if they fall back, they were likely pulled in by a few coordinated installs. Widely deployed utilities that edged down (screenshot-basic, PolyZone, qb-weathersync) are worth no immediate panic — these changes are within normal jitter for large bases — but if you depend on them check for updates or deprecation notes from authors. For new assets that climbed into the 30–40 server band, decide whether to evaluate them for inclusion (they are now visible enough to matter) and watch whether their daily series changes shape: sustained multi-day growth is the best single proxy we have for real adoption. Finally, remember that a week is the shortest window in which adoption is legible; use the 5+ days rule as a screen and treat single-day jumps as prompts to investigate, not as signals to refactor or rip dependencies out.