Working its way up from the back of the class: #14,544 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
32/ 100
F
Lost ground: down 5,288 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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 61% 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
myserver leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 188.0.179.55:28015.
How reliable is myserver, and is it up?
At this moment, myserver is offline; the last time it was seen was 30 days 18 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 27 September 2026.
What Rust version is myserver on?
Rust network protocol 2633 and build 165217 on Windows is what myserver runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does myserver reset?
There are too few wipes on record for myserver to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 31 days 17 hours have passed since this world was made.
Population
Where does myserver sit among Rust servers?
In the top 61% of all ranked servers, myserver sits at #14,544 for player hours over the last seven days.
How many players does myserver usually have?
myserver is offline at the moment; the last time it was seen was 30 days 18 hours ago.
Tags
How should you read the tags on myserver?
The game's browser takes its cue from the tags myserver has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set. 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 myserver appear in the Rust Server Score lists and filters?
Rust Server Score lists that include myserver: 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.
Rules and settings
How is myserver set up, and what rules does it keep?
The name of myserver gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
myserver runs which map?
myserver runs a procedural map, which the game generates.
Getting in
How do you get onto myserver?
To connect, start Rust, press F1, and type client.connect 188.0.179.55:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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. Even marks across the subjects, from F to F.