A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
63/ 100
C
Working its way up from the back of the class: #8,112 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
67/ 100
C+
Keeps a fair share of its players through a wipe: 67% of wipes kept half their crowd.
Momentumrank now against a week ago
43/ 100
F
Slipped a little: down 1,116 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in wipe hold (C+); uptime 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.
AveragePeak
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.
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 37% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
··W··W·
·······
W·WW·W·
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2 daysbetween real wipes
on rhythm29%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 7
The first 48 hours of its last wipes
Sat 24 OctThu 22 OctWed 21 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 12:03 UTC4d ago
1
–
running
0
Thu 22 Oct, 18:37 UTC6d ago
1
–
1.7 days
0
Wed 21 Oct, 16:38 UTC7d ago
1
–
1.1 days
0
Mon 19 Oct, 16:42 UTC9d ago
1
✓ held half
2 days
1
Sat 10 Oct, 09:50 UTC18d ago
2
halved by day 7
9.3 days
0
Wed 7 Oct, 16:53 UTC21d ago
1
✓ held half
2.7 days
0
Sun 4 Oct, 13:09 UTC24d ago
1
✓ held half
3.2 days
0
Sat 3 Oct, 14:45 UTC25d ago
1
–
0.9 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
You'll find no region listed by Rust Staging (dev). Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 62.64.144.83:16347.
How reliable is Rust Staging (dev), and is it up?
You cannot join now: Rust Staging (dev) is offline, last seen 25 hours ago. For the last 7 full days, it was up 29 of 168 hours, or 17% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
What Rust version is Rust Staging (dev) on?
Rust network protocol 2635 and build 169399 on Windows is what Rust Staging (dev) runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does Rust Staging (dev) wipe, and how often?
Rust Staging (dev) wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 4 days 9 hours have passed since this world was made.
What should you expect from wipe day on Rust Staging (dev)?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 1 hours after it began. Above half the peak until the next wipe: that was the pattern in 67% of its recent wipes. The crowd dropped below half by day 7 in the wipes where it did not hold.
Player count
Where does Rust Staging (dev) place in the wider field of Rust servers?
Over the last seven days, Rust Staging (dev) has #8,112 for player hours, in the top 37% of all ranked servers.
Is Rust Staging (dev) a busy server?
The last sighting of Rust Staging (dev) was 25 hours ago, and it is offline right now. The seven-day average is 1 players, with a peak of 1. The highest average in the last 48 hours came at 20:00 UTC, with 1 players.
Lists and filters
What do Rust Staging (dev)'s tags stand for?
gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs169399 (Build): The game build is 169399; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags Rust Staging (dev) 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 Rust Staging (dev) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust Staging (dev) among them: Best community servers, graded. These filters bring it up 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 week.
Map and rules
Which rules does Rust Staging (dev) enforce, and what are its settings?
You will find no gather rate in the name of Rust Staging (dev). With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: 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 Rust Staging (dev) uses?
Rust Staging (dev) runs a procedural map, which the game generates.
Getting in
What is the way to join Rust Staging (dev)?
Enter client.connect 62.64.144.83:16347 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 asmp10,ptrak,$r?,v2635,gmvanilla,cs169399,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs169399
BuildThe game build is 169399.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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 wipe hold (C+); uptime is the one to work on (F).