Working its way up from the back of the class: #15,426 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
52/ 100
D
Moving up: up 551 places this week.
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 71% 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h.
The 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 420. Rust Server Score takes the server's word for its location and does not trace the hardware. 201.219.67.14:28015 is the address to use.
Is 420 up, and how steady is its uptime?
The server is down: 420 is offline now, with the last sighting 16 days 5 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 13 October 2026, Rust Server Score saw it for the first time.
On what Rust version does 420 sit?
You will find 420 on Rust network protocol 2634 and build 167584, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does 420 wipe its map?
The estimate for 420's next wipe comes from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 16 days 5 hours. Its tags list a monthly wipe schedule.
Population
Where does 420 place in the wider field of Rust servers?
In the top 71% of all ranked servers, 420 sits at #15,426 for player hours over the last seven days.
What does the population on 420 look like?
420 is offline at the moment; the last time it was seen was 16 days 5 hours ago.
Lists and filters
What is meant by the tags on 420?
gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): 100 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags 420 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 420 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include 420: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on 420?
The name of 420 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. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map 420 uses?
The game generates a procedural map for 420.
Getting in
How should you connect to 420?
To connect, start Rust, press F1, and type client.connect 201.219.67.14:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^m,gmvanilla,cs167584,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max players100 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167584
BuildBuild number: 167584.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
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).