Working its way up from the back of the class: #13,672 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
26/ 100
F
Lost ground: down 6,454 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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.
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 62% 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 gap4 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Thu 8 OctSun 4 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 10:21 UTC19d ago
1
–
running
1
Sun 4 Oct, 09:42 UTC23d ago
1
halved by day 1
4 days
1
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
3am17 staging test leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 83.17.151.145:28015 is the address to use.
How reliable is 3am17 staging test, and is it up?
You cannot join now: 3am17 staging test is offline, last seen 19 days 12 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does 3am17 staging test sit?
Rust network protocol 2634 and build 166655 on Windows is what 3am17 staging test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does 3am17 staging test wipe, and how often?
The record holds too few of 3am17 staging test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 19 days 13 hours have passed since this world was made.
What happens on 3am17 staging test when wipe day arrives?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player numbers
Where does 3am17 staging test sit among Rust servers?
In the top 62% of all ranked servers, 3am17 staging test sits at #13,672 for player hours over the last seven days.
Is 3am17 staging test a busy server?
The last sighting of 3am17 staging test was 19 days 12 hours ago, and it is offline right now.
Tags
What do 3am17 staging test's tags stand for?
The game's browser takes its cue from the tags 3am17 staging test has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp20 (Max players): The server holds 20 slots; 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; cs166655 (Build): The game build is 166655; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature 3am17 staging test?
These Rust Server Score lists count 3am17 staging test 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.
Map and rules
How is 3am17 staging test set up, and what rules does it keep?
The name of 3am17 staging test gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on 3am17 staging test?
The game generates a procedural map for 3am17 staging test.
Getting in
How do you get onto 3am17 staging test?
To connect, start Rust, press F1, and type client.connect 83.17.151.145:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2634,gmrust,cs166655,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp20
Max playersThe server holds 20 slots.
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.
cs166655
BuildThe game build is 166655.
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 standing (F); wipes are the one to work on (F).