On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,353top 69%
Last wipe9d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,353 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 94 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
41/ 100
F
Slipped a little: down 2,769 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 19 Oct. 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
No region is published for Atlas Rust Test 01. Rust Server Score takes the server's word for its location and does not trace the hardware. 64.40.8.137:28015 is the address to use.
How reliable is Atlas Rust Test 01, and is it up?
The server is up: Atlas Rust Test 01 is online now. The uptime it reports puts the last restart at about 9 days 21 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 19 October 2026.
How well does Atlas Rust Test 01 run?
The average over the last 48 hours was 94 server fps, and it never went below 84. At its peak, it held 120,462 entities, including buildings, deployables and all else in the world. At its highest, it used 5,081 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does Atlas Rust Test 01 sit?
The server Atlas Rust Test 01 is on Rust network protocol 2634 and build 167781 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Atlas Rust Test 01 wipe, and how often?
There are too few wipes on record for Atlas Rust Test 01 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 9 days 23 hours have passed since this world was made.
Population
Where does Atlas Rust Test 01 place in the wider field of Rust servers?
Over the last seven days, Atlas Rust Test 01 has #15,353 for player hours, in the top 69% of all ranked servers.
How many players does Atlas Rust Test 01 usually have?
Atlas Rust Test 01 is showing 0 players right now, with 50 slots in total. For the last seven days, the average number of players was 0.
Tags
What do Atlas Rust Test 01's tags stand for?
The game's browser takes its cue from the tags Atlas Rust Test 01 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Atlas Rust Test 01?
These Rust Server Score lists count Atlas Rust Test 01 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is Atlas Rust Test 01 set up, and what rules does it keep?
The name of Atlas Rust Test 01 gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Atlas Rust Test 01 uses?
Atlas Rust Test 01 runs a game-generated procedural map at size 4,500, seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to Atlas Rust Test 01?
Enter client.connect 64.40.8.137:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://atlastool.shop.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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 performance (A+); population is the one to work on (F).