Rust Server TrendsSeismic network · station log
Recording Stations11,802 Players70,703 Active3,677 Wipes · 3 h121 48 h

Station XX-15274 · no signal

Yasuhiko Rust Solo

Offline 119.150.87.70:28025 checked 9d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,274
top 69%
Last wipe
32d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15274 · 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
15k10k15k20k20 Sep24 Sep15 Oct19 Oct22 Oct26 Oct

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 13 Oct, 08:38 UTC15d ago M0.0steady 1 – running 1

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 · 553 on average
510/ 575
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
340/ 400
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 297 on average
39/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 296 on average
36/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 272 on average
109/ 150
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 253 on average
125/ 200
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Yasuhiko Rust Solo?

The map on Yasuhiko Rust Solo is procedural, produced 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. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.

Live population

How many players are recorded on Yasuhiko Rust Solo right now?

A reading taken now finds Yasuhiko Rust Solo offline; the most recent activity was 9 days 19 hours ago.

How does Yasuhiko Rust Solo rank against other Rust servers?

The last seven days of player hours place Yasuhiko Rust Solo at #15,274, in the top 69% of all ranked servers.

Server facts

How reliably does Yasuhiko Rust Solo stay online?

No contact with Yasuhiko Rust Solo right now, and the last recorded contact was 9 days 19 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 16 September 2026 is when Rust Server Trends first recorded it.

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:28025 is the address it uses.

Which Rust version is Yasuhiko Rust Solo running?

Rust network protocol 2633 and build 165217 on Linux is what Yasuhiko Rust Solo runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on Yasuhiko Rust Solo?

On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.

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. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 32 days 8 hours is how long the current world has been running.

Server 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): Game protocol 2633: to join, your game must match this version; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server. The tags also carry its current players, its queue and when its world was made, shown 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

How do you connect to Yasuhiko Rust Solo?

You can connect by pressing F1 in Rust and typing client.connect 119.150.87.70:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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 Game protocol 2633: to join, your game must match this version.
cs165217
Build The game build is 165217.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

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.