Working its way up from the back of the class: #15,348 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
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.
No daily history yet.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 22 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
In what location does Atlas Benchmark X3D2 (temp) sit?
You'll find no region listed by Atlas Benchmark X3D2 (temp). Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 195.60.166.62:28020.
How dependable is Atlas Benchmark X3D2 (temp), and is it online at the moment?
At this moment, Atlas Benchmark X3D2 (temp) is offline; the last time it was seen was 6 days 9 hours ago. It was up 0% of the time over the last 5 full days, 0 of 120 hours. On 22 October 2026, Rust Server Score saw it for the first time.
Which Rust version is Atlas Benchmark X3D2 (temp) running?
Rust network protocol 2634 and build 167781 on Linux is what Atlas Benchmark X3D2 (temp) runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Atlas Benchmark X3D2 (temp) wipe, and how often?
The record holds too few of Atlas Benchmark X3D2 (temp)'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 13 days 5 hours.
Player count
What position does Atlas Benchmark X3D2 (temp) hold in the rankings?
Over the last seven days, Atlas Benchmark X3D2 (temp) has #15,348 for player hours, in the top 69% of all ranked servers.
Is Atlas Benchmark X3D2 (temp) a busy server?
The last sighting of Atlas Benchmark X3D2 (temp) was 6 days 9 hours ago, and it is offline right now. For the last seven days, the average number of players was 0.
Tags
How should you read the tags on Atlas Benchmark X3D2 (temp)?
gmvanilla (Game mode): This is vanilla survival; mp0 (Max players): Its slot count is 0; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here are the tags Atlas Benchmark X3D2 (temp) publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Atlas Benchmark X3D2 (temp)?
Rust Server Score lists that include Atlas Benchmark X3D2 (temp): Best community servers, graded. It shows under the following filters on the server list: 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
What settings and rules apply on Atlas Benchmark X3D2 (temp)?
You will find no gather rate in the name of Atlas Benchmark X3D2 (temp). The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. 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 Benchmark X3D2 (temp) uses?
The game generates the procedural map on Atlas Benchmark X3D2 (temp) at size 5,000 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Connecting
How should you connect to Atlas Benchmark X3D2 (temp)?
Enter client.connect 195.60.166.62:28020 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 asmp0,ptrak,$r?,v2634,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp0
Max playersIts slot count is 0.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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.