Working its way up from the back of the class: #15,503 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 8,997 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (A+); momentum 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.
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.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
·W·W·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 rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Sat 19 SepThu 17 SepTue 15 Sep
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
Sat 19 Sep, 19:58 UTC39d ago
1
–
running
1
Thu 17 Sep, 16:49 UTC41d ago
1
✓ held half
2.1 days
1
Tue 15 Sep, 17:03 UTC43d ago
3
–
2 days
0
Sun 13 Sep, 19:02 UTC45d ago
3
–
1.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
Server Unavailable! leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 157.85.86.101:28871 is the address to use.
Is Server Unavailable! up, and how steady is its uptime?
You cannot join now: Server Unavailable! is offline, last seen 37 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is Server Unavailable! on?
The server Server Unavailable! is on Rust network protocol 2633 and build 164530 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Server Unavailable! wipe, and how often?
No next wipe can be predicted for Server Unavailable!, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 39 days 5 hours have passed since this world was made.
What happens on Server Unavailable! when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. 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 100% of its recent wipes.
Player count
Where does Server Unavailable! sit among Rust servers?
Over the last seven days, Server Unavailable! has #15,503 for player hours, in the top 67% of all ranked servers.
How many players does Server Unavailable! usually have?
The last sighting of Server Unavailable! was 37 days 20 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Server Unavailable!?
gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): 40 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Server Unavailable! 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 Server Unavailable! appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Server Unavailable!: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does Server Unavailable! enforce, and what are its settings?
You will find no gather rate in the name of Server Unavailable!. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Server Unavailable!?
The game generates the procedural map on Server Unavailable! at size 4,250 with seed 1509017534. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
What is the way to join Server Unavailable!?
Enter client.connect 157.85.86.101:28871 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 asmp40,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max players40 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
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 (A+); momentum is the one to work on (F).