Working its way up from the back of the class: #13,622 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
51/ 100
D
Moving up: up 236 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No daily history yet.
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 62% 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
You'll find no region listed by My Solo Test Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 109.121.44.60:28015 is the address to use.
How reliable is My Solo Test Server, and is it up?
You cannot join now: My Solo Test Server is offline, last seen 20 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 8 October 2026, Rust Server Score saw it for the first time.
What Rust version is My Solo Test Server on?
Rust network protocol 2634 and build 167231 on Windows is what My Solo Test Server runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does My Solo Test Server reset?
There are too few wipes on record for My Solo Test Server 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. 20 days 2 hours have passed since this world was made.
Population
Where does My Solo Test Server place in the wider field of Rust servers?
Over the last seven days, My Solo Test Server has #13,622 for player hours, in the top 62% of all ranked servers.
What does the population on My Solo Test Server look like?
It has been 20 days 2 hours since My Solo Test Server was last seen, and it is offline right now.
Lists and filters
What do My Solo Test Server's tags stand for?
You'll see My Solo Test Server tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): 5 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167231 (Build): This runs on build 167231; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. 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 Test Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include My Solo Test Server: Best community servers, graded. It shows under the following filters 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 My Solo Test Server set up, and what rules does it keep?
Nothing in the name of My Solo Test Server states a gather rate. 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. You can raid other players and fight them. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Connecting
How do you get onto My Solo Test Server?
Enter client.connect 109.121.44.60: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 asmp5,ptrak,$r?,v2634,gmrust,cs167231,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max players5 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167231
BuildThis runs on build 167231.
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 momentum (D); standing is the one to work on (F).