The current official record verifies first-to-five 1v1–5v5 FPS duels, duel pads, keys, weapons, skins, contracts, win streaks, leaderboards, broad device support, Update 21, and a Summer Event. It does not publish a complete weapon or map dataset, balance values, contract rewards, event patch notes, codes, or rankings by weapon.
Identity and current official record
RIVALS is universe 6035872082 with root place 17625359962, published by verified Roblox group Nosniy Games. At the August 21 check, the official API showed roughly 255,000 concurrent players and more than 17.5 billion visits. Those counters establish current scale, not future popularity or any mechanic. Identity follows the universe and root place even when the title carries an update label. Results for another experience, a sports rivalry, or a similarly named shooter are rejected. The official genre is FPS, but genre alone does not define the current modes, competitive rules, progression economy, or balance model.
Verified match structure
The creator explicitly describes 1v1 through 5v5 FPS duels in which the first side to five wins and tells players to challenge someone by stepping on a duel pad. These are verified structural claims. The source does not enumerate maps, round timers, overtime, team formation, queue priority, ranked divisions, private-server differences, spawn rules, or tie handling. A player capture may show one current implementation, but it must include the exact place, date, mode, and visible outcome before a detail becomes observed. A guide from an older update cannot override a changed live prompt.
Keys, weapons, skins, and contracts
Roblox currently states that players earn keys to unlock weapons and skins and complete contracts for exclusive rewards. This verifies four system families and their broad relationship. It does not provide the key earning formula, permanent price schedule, complete weapon or skin roster, contract rotation, reward inventory, rarity order, or statistical effects. Creator images can help recognize current presentation but remain promotional snapshots. A weapon shown in art is not automatically available to every account, and a number visible in an image is not a stable balance table. Data-heavy claims stay unknown until a current attributable source supplies every relevant row and limitation.
Win streaks, leaderboards, and awards
The official description invites players to show a win streak and climb leaderboards, confirming that these result surfaces exist. It does not define ranking formulas, reset dates, eligible modes, anti-abuse filters, rewards, or how ties are handled. The badge endpoint currently exposes Welcome and Alpha Tester labels. Welcome only thanks the player for playing, while Alpha Tester thanks early testers; neither description verifies a combat achievement, rank, currency reward, or present-day acquisition path beyond its text. Do not turn a badge name, streak screenshot, or leaderboard position into a universal progression requirement.
Update 21 and Summer Event boundary
The current creator text announces Update 21 and the first RIVALS Summer Event, then points players to in-game patch notes. That is enough to verify the update label and event wording at the checked time. The public virtual-event endpoint returned no event record, so this reference does not invent dates, rewards, quests, maps, items, or expiration. An in-game patch note can become evidence only when it is captured with the current server and attributable version. Preserve conflicts when a player video, promotional thumbnail, and live client show different states instead of merging them into one synthetic update list.
Held codes, tiers, stats, and routes
This package deliberately holds Codes, weapon tier lists, damage and recoil tables, map routes, contract-reward tables, key calculators, event checklists, and best-loadout claims. The checked creator description contains no code string, expiry, reward, or redemption workflow. The media set and current videos are not complete comparable datasets. To publish one of these families later, QuestSignal needs exact current labels, attributable values or reproducible before-and-after captures, comparison criteria, limitations, and a refresh trigger. Popularity, search volume, or a high-view clip can prioritize that work but cannot fill a missing factual field.
What changed across observed Roblox snapshots
This is our own dated history of the same public Roblox fields. It shows observed movement, not a prediction or an explanation for why players moved.
Source: QuestSignal immutable release history · newest five observations shown
What this guide does not assume
This wiki verifies exact identity, the creator-stated duel and progression structure, current update wording, broad device support, and two official badge descriptions. It does not certify weapon or skin rosters, stats, ranks, maps, contracts, rewards, key rates, event details, codes, or tier placements.
Refresh trigger: Refresh when Roblox changes the identity, title, description, media, badges, event record, duel format, progression wording, or an attributable current capture resolves a held dataset.