Working its way up from the back of the class: #16,275 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 164 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is Atlas - 10x Development (Staging)?
Atlas - 10x Development (Staging) leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 64.40.8.251:28160.
Is Atlas - 10x Development (Staging) up, and how steady is its uptime?
At this moment, Atlas - 10x Development (Staging) is offline; the last time it was seen was 27 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 29 September 2026, Rust Server Score saw it for the first time.
What Rust version is Atlas - 10x Development (Staging) on?
The server Atlas - 10x Development (Staging) is on Rust network protocol 2634 and build 166257 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Atlas - 10x Development (Staging) reset?
There are too few wipes on record for Atlas - 10x Development (Staging) to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 29 days 5 hours have passed since this world was made.
Player numbers
Where does Atlas - 10x Development (Staging) place in the wider field of Rust servers?
In the top 69% of all ranked servers, Atlas - 10x Development (Staging) sits at #16,275 for player hours over the last seven days.
How many players does Atlas - 10x Development (Staging) usually have?
The last sighting of Atlas - 10x Development (Staging) was 27 days 5 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Atlas - 10x Development (Staging)?
gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): Its slot count is 100; ts30 (Group limit): A team can hold 30 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166257 (Build): The game build is 166257; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; modded (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Atlas - 10x Development (Staging) publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Atlas - 10x Development (Staging) appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Atlas - 10x Development (Staging): 10x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 10x.
Rules and settings
What settings and rules apply on Atlas - 10x Development (Staging)?
Going by its name, Atlas - 10x Development (Staging) runs 10x gather. You can play in groups of up to 30 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
How to join
How do you get onto Atlas - 10x Development (Staging)?
Enter client.connect 64.40.8.251:28160 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^v,gmvanilla,cs166257,ts30,^o^z,modded
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersIts slot count is 100.
ts30
Group limitA team can hold 30 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166257
BuildThe game build is 166257.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
modded
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).