Working its way up from the back of the class: #13,383 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
25/ 100
F
Lost ground: down 6,612 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); 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 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
No region is published for My Solo Sandbox. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 153.173.194.128:28015 is the address to use.
Is My Solo Sandbox up, and how steady is its uptime?
You cannot join now: My Solo Sandbox is offline, last seen 17 days 19 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 7 October 2026.
On what Rust version does My Solo Sandbox sit?
You will find My Solo Sandbox 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
When does My Solo Sandbox wipe, and how often?
There are too few wipes on record for My Solo Sandbox to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 22 days 19 hours.
Population
Where does My Solo Sandbox place in the wider field of Rust servers?
Over the last seven days, My Solo Sandbox has #13,383 for player hours, in the top 61% of all ranked servers.
What does the population on My Solo Sandbox look like?
It has been 17 days 19 hours since My Solo Sandbox was last seen, and it is offline right now.
Tags and filters
What do My Solo Sandbox's tags stand for?
The game's browser takes its cue from the tags My Solo Sandbox has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show My Solo Sandbox?
These Rust Server Score lists count My Solo Sandbox among them: Rust build and creative servers and 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 Sandbox set up, and what rules does it keep?
You will find no gather rate in the name of My Solo Sandbox. 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. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map My Solo Sandbox uses?
My Solo Sandbox runs a procedural map, which the game generates.
How to join
How should you connect to My Solo Sandbox?
Enter client.connect 153.173.194.128:28015 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 asmp1,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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); momentum is the one to work on (F).