Working its way up from the back of the class: #12,154 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
28/ 100
F
Lost ground: down 5,322 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (D); 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.
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 55% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
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
Mon 5 Oct, 11:16 UTC22d ago
1
–
running
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
My Solo Server leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 4.8.116.142:28015.
How reliable is My Solo Server, and is it up?
At this moment, My Solo Server is offline; the last time it was seen was 20 days 15 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 15 September 2026.
Which Rust version is My Solo Server running?
You will find My Solo Server on Rust network protocol 2634 and build 166652, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does My Solo Server reset?
There are too few wipes on record for My Solo Server 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 22 days 17 hours.
What happens on My Solo Server 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.
Player count
What position does My Solo Server hold in the rankings?
Over the last seven days, My Solo Server has #12,154 for player hours, in the top 55% of all ranked servers.
What does the population on My Solo Server look like?
My Solo Server is offline at the moment; the last time it was seen was 20 days 15 hours ago.
Tags and filters
What is meant by the tags on My Solo Server?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp2 (Max players): Its slot count is 2; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags My Solo Server publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does My Solo Server appear in the Rust Server Score lists and filters?
These Rust Server Score lists count My Solo Server among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
How is My Solo Server set up, and what rules does it keep?
The name of My Solo Server gives no gather rate. The group limit stays at the game's default of 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 under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
My Solo Server runs which map?
A procedural map, generated by the game, is what My Solo Server runs.
Connecting
How do you get onto My Solo Server?
To connect, start Rust, press F1, and type client.connect 4.8.116.142:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp2
Max playersIts slot count is 2.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThe game build is 166652.
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 (D); momentum is the one to work on (F).