RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers119.150.87.70:28025
Offline Full Queue Fresh wipe Wipe due No query

Yasuhiko Rust Solo

Offline 119.150.87.70:28025 checked 9d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,274top 69%
Last wipe32d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

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.

PLAN

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 peak1players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 08:38 UTC15d ago 1 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Yasuhiko Rust Solo?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Yasuhiko Rust Solo follow?

Its rhythm cannot be told from the wipes of Yasuhiko Rust Solo on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 32 days 7 hours ago the current world was made.

Tag meanings

Which tags does Yasuhiko Rust Solo carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from Yasuhiko Rust Solo. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Yasuhiko Rust Solo?

On Rust Metrics, Yasuhiko Rust Solo sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Yasuhiko Rust Solo hold among Rust servers?

Player hours over seven days put Yasuhiko Rust Solo at #15,274, in the top 69% of all ranked servers.

What player count does Yasuhiko Rust Solo carry?

Yasuhiko Rust Solo is not responding; status offline, last seen 9 days 18 hours ago.

Server

Which location does Yasuhiko Rust Solo run from?

No region tag on Yasuhiko Rust Solo. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 119.150.87.70:28025.

What Rust version is Yasuhiko Rust Solo on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by Yasuhiko Rust Solo. Matching protocol is required to join. Let Steam update your game.

Is Yasuhiko Rust Solo up, and how often does it stay up?

Check: connection. Yasuhiko Rust Solo is offline at this moment. Last contact was 9 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 16 September 2026.

Settings and map

What settings and rules apply on Yasuhiko Rust Solo?

Reading the name gives no gather rate for Yasuhiko Rust Solo. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is Yasuhiko Rust Solo on?

Procedural map on Yasuhiko Rust Solo, made by the game's generator.

Connection

What do you do to join Yasuhiko Rust Solo?

Check: join. Open Rust, press F1, then enter client.connect 119.150.87.70:28025. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.