Working its way up from the back of the class: #14,220 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
18/ 100
F
Lost ground: down 9,037 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
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
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 gap1 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Wed 23 SepMon 21 SepSun 20 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
Wed 23 Sep, 15:31 UTC34d ago
1
–
running
1
Mon 21 Sep, 10:30 UTC36d ago
1
–
2.2 days
1
Sun 20 Sep, 10:38 UTC37d ago
1
–
1 days
0
Sat 19 Sep, 12:50 UTC38d ago
1
–
0.9 days
1
Sat 19 Sep, 06:25 UTC38d ago
1
–
0.3 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
My Solo Rust World leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 49.36.170.3:28015.
How reliable is My Solo Rust World, and is it up?
The server is down: My Solo Rust World is offline now, with the last sighting 31 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 15 September 2026, Rust Server Score saw it for the first time.
On what Rust version does My Solo Rust World sit?
Rust network protocol 2633 and build 162929 on Linux is what My Solo Rust World runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does My Solo Rust World wipe its map?
No next wipe can be predicted for My Solo Rust World, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 34 days 11 hours have passed since this world was made.
What should you expect from wipe day on My Solo Rust World?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does My Solo Rust World sit among Rust servers?
In the top 61% of all ranked servers, My Solo Rust World sits at #14,220 for player hours over the last seven days.
Is My Solo Rust World a busy server?
The last sighting of My Solo Rust World was 31 days 18 hours ago, and it is offline right now.
Tags and filters
What do My Solo Rust World's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): Its slot count is 1; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): Build number: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags My Solo Rust World 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.
Which lists and filters on Rust Server Score show My Solo Rust World?
Rust Server Score lists that include My Solo Rust World: 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.
Map and rules
How is My Solo Rust World set up, and what rules does it keep?
Nothing in the name of My Solo Rust World states a gather rate. With no change from the game default, groups take up to 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 as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are not covered by VAC, Valve's anti-cheat.
My Solo Rust World runs which map?
The game generates a procedural map for My Solo Rust World.
How to join
How should you connect to My Solo Rust World?
To connect, start Rust, press F1, and type client.connect 49.36.170.3: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,cs162929,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersIts slot count is 1.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildBuild number: 162929.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 standing (F); momentum is the one to work on (F).