Working its way up from the back of the class: #15,193 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 656 places this week.
A term to build on.
Strongest in momentum (D); wipes are 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.
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 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap13.2 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 5
The first 48 hours of its last wipes
Fri 2 OctSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 19:41 UTC26d ago
2
–
running
0
Sat 19 Sep, 14:11 UTC40d ago
2
halved by day 5
13.2 days
0
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
Area 420 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 208.115.251.67:28080.
Is Area 420 up, and how steady is its uptime?
At this moment, Area 420 is offline; the last time it was seen was 12 days 11 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does Area 420 sit?
You will find Area 420 on Rust network protocol 2634 and build 166586, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Area 420 wipe its map?
There are too few wipes on record for Area 420 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. It has been running its current world for 26 days 22 hours.
What should you expect from wipe day on Area 420?
Across its recent wipes, the busiest moments averaged 2 players. 2 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 5 is when it sank below half in the wipes that did not hold.
Population
Where does Area 420 place in the wider field of Rust servers?
Over the last seven days, Area 420 has #15,193 for player hours, in the top 70% of all ranked servers.
Is Area 420 a busy server?
Area 420 is offline at the moment; the last time it was seen was 12 days 11 hours ago.
Tags
How should you read the tags on Area 420?
You'll see Area 420 tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166586 (Build): The game build is 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Area 420?
These Rust Server Score lists count Area 420 among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Area 420?
You will find no gather rate in the name of Area 420. 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 as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Area 420 runs which map?
A procedural map of size 3,500 and seed 481981, generated by the game, is what Area 420 runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How should you connect to Area 420?
Enter client.connect 208.115.251.67:28080 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 asmp50,ptrak,$r?,v2634,gmrust,cs166586,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166586
BuildThe game build is 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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); wipes are the one to work on (F).