Rust Server TrendsSeismic network · station log
Recording Stations11,636 Players40,778 Active2,957 Wipes · 3 h88 48 h

Station XX-14486 · no signal

Yasuhiko Rust Solo

Offline 119.150.87.70:28035 checked 13d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,486
top 67%
Last wipe
31d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-14486 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 1 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k15 Oct16 Oct18 Oct19 Oct21 Oct22 Oct

Top 67% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 527 on average
270/ 300
Rustoria.co - EU Main EU · groups of 16+ · weekly · 331 on average
16/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 329 on average
34/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
117/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 279 on average
45/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 264 on average
50/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Yasuhiko Rust Solo?

A procedural map runs on Yasuhiko Rust Solo, generated by the game.

Which settings and rules apply on Yasuhiko Rust Solo?

The name of Yasuhiko Rust Solo gives no gather rate. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on Yasuhiko Rust Solo?

Yasuhiko Rust Solo is not responding at this moment and is offline, last seen 13 days ago.

How does Yasuhiko Rust Solo rank against other Rust servers?

The last seven days of player hours place Yasuhiko Rust Solo at #14,486, in the top 67% of all ranked servers.

Operator and location

How reliably does Yasuhiko Rust Solo stay online?

Yasuhiko Rust Solo is down at the moment; the last recorded contact was 13 days ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 15 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does Yasuhiko Rust Solo run from?

A region is not published by Yasuhiko Rust Solo. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 119.150.87.70:28035 is the address it uses.

Which Rust version is Yasuhiko Rust Solo running?

On Linux, Yasuhiko Rust Solo runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

How often does Yasuhiko Rust Solo wipe, and on which days?

The rhythm of Yasuhiko Rust Solo cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 31 days 13 hours.

Lists and tags

What do the server tags on Yasuhiko Rust Solo mean?

Tags published by Yasuhiko Rust Solo and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): 1 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): It runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Yasuhiko Rust Solo appear?

These Rust Server Trends lists include Yasuhiko Rust Solo: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto Yasuhiko Rust Solo?

Enter client.connect 119.150.87.70:28035 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp1
Max players 1 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build It runs game build 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.