Working its way up from the back of the class: #15,339 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 214 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.
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.
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 Benchmark 14900KS (temp)?
Atlas Benchmark 14900KS (temp) leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 208.52.153.63:28020 is the address to use.
Is Atlas Benchmark 14900KS (temp) up, and how steady is its uptime?
The server is down: Atlas Benchmark 14900KS (temp) is offline now, with the last sighting 6 days 20 hours ago. It was up 0% of the time over the last 6 full days, 0 of 144 hours. On 22 October 2026, Rust Server Score saw it for the first time.
What Rust version is Atlas Benchmark 14900KS (temp) on?
Rust network protocol 2634 and build 167781 on Linux is what Atlas Benchmark 14900KS (temp) runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does Atlas Benchmark 14900KS (temp) wipe, and how often?
There are too few wipes on record for Atlas Benchmark 14900KS (temp) to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 13 days 15 hours.
Population
Where does Atlas Benchmark 14900KS (temp) sit among Rust servers?
In the top 69% of all ranked servers, Atlas Benchmark 14900KS (temp) sits at #15,339 for player hours over the last seven days.
How many players does Atlas Benchmark 14900KS (temp) usually have?
It has been 6 days 20 hours since Atlas Benchmark 14900KS (temp) was last seen, and it is offline right now. Over the past seven days, the average player count was 0.
Tags
How should you read the tags on Atlas Benchmark 14900KS (temp)?
You'll see Atlas Benchmark 14900KS (temp) tagged with gmvanilla (Game mode): You play vanilla survival here; mp0 (Max players): 0 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the 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 Rust Server Score filters and lists feature Atlas Benchmark 14900KS (temp)?
These Rust Server Score lists count Atlas Benchmark 14900KS (temp) among them: 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.
Server rules
Which rules does Atlas Benchmark 14900KS (temp) enforce, and what are its settings?
You will find no gather rate in the name of Atlas Benchmark 14900KS (temp). With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Connecting
How do you get onto Atlas Benchmark 14900KS (temp)?
To connect, start Rust, press F1, and type client.connect 208.52.153.63:28020. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeYou play vanilla survival here.
mp0
Max players0 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Strongest in momentum (D); standing is the one to work on (F).