Working its way up from the back of the class: #14,486 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
53/ 100
D
Moving up: up 733 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 67% 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 Yasuhiko Rust Solo. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 119.150.87.70:28035 is the address to use.
Is Yasuhiko Rust Solo up, and how steady is its uptime?
You cannot join now: Yasuhiko Rust Solo is offline, last seen 13 days 1 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 15 October 2026.
What Rust version is Yasuhiko Rust Solo on?
The server Yasuhiko Rust Solo is on Rust network protocol 2633 and build 165217 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Yasuhiko Rust Solo wipe its map?
The record holds too few of Yasuhiko Rust Solo's wipes to tell its 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 31 days 14 hours.
Player numbers
What position does Yasuhiko Rust Solo hold in the rankings?
In the top 67% of all ranked servers, Yasuhiko Rust Solo sits at #14,486 for player hours over the last seven days.
How many players does Yasuhiko Rust Solo usually have?
It has been 13 days 1 hours since Yasuhiko Rust Solo was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Yasuhiko Rust Solo?
The game's browser takes its cue from the tags Yasuhiko Rust Solo has set: gmrust (Game mode): Survival in the standard Rust style; 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; cs165217 (Build): This runs on build 165217; 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 Yasuhiko Rust Solo?
Rust Server Score lists that include Yasuhiko Rust Solo: 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 Yasuhiko Rust Solo set up, and what rules does it keep?
Nothing in the name of Yasuhiko Rust Solo states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, 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. You are covered by VAC, Valve's anti-cheat.
Yasuhiko Rust Solo runs which map?
Yasuhiko Rust Solo runs a procedural map, which the game generates.
Getting in
How should you connect to Yasuhiko Rust Solo?
Enter client.connect 119.150.87.70:28035 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?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
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.
cs165217
BuildThis runs on build 165217.
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 momentum (D); standing is the one to work on (F).