Rust HeatmapInfrared · players
IR live Players80,805 Servers11,809 Warm3,802 Fresh wipes · 3h104 Frameevery 5 min
‹ All serversThermal scan
REC Thermal scan · 48 h Sp1 1° now Linear · 0–1° · slots

Yasuhiko Rust Solo

Offline 119.150.87.70:28015 checked 2d ago

Sp1 · players now 1/ 1
100% full
Li1 · players, the last 48 hours · hourly average, UTC
No hourly readings in the last 48 hours
1
7-day average
peak 1
#5,289
rank
top 24%
32d ago
last wipe
no schedule published
–
next wipe
no rhythm it keeps
UTC checked 2d ago

Li2Players

No hourly history yet.

Hourly average and peak, UTC.

Li3Server 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.

Li4Rank

daily · 1 is best
RankRank in region
12k4k6k8k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Bx1Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

7 days
usual gap
between real wipes
100%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctFri 25 SepFri 18 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Bx2Wipes

newest first · each peak a flare-up, on one √ span to its biggest
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 03:16 UTC26d ago 1 – running 0
Fri 25 Sep, 02:06 UTC33d ago 1 held half 7 days 1
Fri 18 Sep, 02:48 UTC40d ago 1 held half 7 days 0

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.

Bx6Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays|
EU · groups of 12+ · weekly · 552 on average
605 / 675
Rustoria.co - EU East Long
EU · groups of 12+ · monthly · 318 on average
377 / 525
Rusty Moose |EU Main|
EU · groups of 12+ · weekly · 299 on average
47 / 250
Rustoria.co - EU Main
EU · groups of 16+ · weekly · 298 on average
35 / 250
Rustafied.com - EU Friday
EU · groups of 16+ · weekly · 271 on average
137 / 200
Rustoria.co - EU East Medium
EU · groups of 12+ · biweekly · 254 on average
160 / 300

LogQuick answers

from the figures on this page

Wipe day

What does wipe day look like on Yasuhiko Rust Solo?

The average peak across its recent wipes is 1 players. 3 hours after the latest wipe, the crowd peaked. Above half the peak until the next wipe: that held in 100% of its recent wipes.

What is the wipe schedule on Yasuhiko Rust Solo?

Wipes come at irregular times on Yasuhiko Rust Solo, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 32 days 7 hours ago the server made the world it is on now.

Population

How busy is Yasuhiko Rust Solo?

The last time Yasuhiko Rust Solo was seen was 2 days 15 hours ago, and it is offline now. A seven-day average of 1 players, with a peak of 1.

How does Yasuhiko Rust Solo rank against other Rust servers?

Player hours over seven days put Yasuhiko Rust Solo at #5,289, in the top 24% of ranked servers.

Rules and settings

Which map does Yasuhiko Rust Solo run?

Yasuhiko Rust Solo runs a procedural map, which the game generates.

What are the rules and settings on Yasuhiko Rust Solo?

The name Yasuhiko Rust Solo does not specify a gather rate. The group limit is 8 players, which is the game's default. The server runs survival, standard play: gathering, building and raiding. Players can fight each other, and raids are allowed. The server browser lists it under Community. The server has VAC, Valve's anti-cheat, turned on.

Location and uptime

Which version of Rust does Yasuhiko Rust Solo run?

Rust network protocol 2633 and build 165217 is the build Yasuhiko Rust Solo runs, on Linux. To join, your game must match the protocol; Steam handles the update.

Is Yasuhiko Rust Solo online, and how reliable is it?

Yasuhiko Rust Solo is down just now; the last sighting was 2 days 15 hours ago. It was up 45 of 168 hours across the last 7 full days, or 27% of the time. The first record of it on Rust Heatmap is 14 September 2026.

Where is Yasuhiko Rust Solo located?

No region is published by Yasuhiko Rust Solo. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. You can reach it at 119.150.87.70:28015.

Lists and filters

Which Rust Heatmap lists and filters include Yasuhiko Rust Solo?

These Rust Heatmap lists include Yasuhiko Rust Solo: Best Rust community servers. These are the filters that return it on the list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

What do the server tags on Yasuhiko Rust Solo mean?

These are the tags Yasuhiko Rust Solo publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): The server runs game protocol 2633, so your game has to match it; cs165217 (Build): Build 165217; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.

Connect

How do I join Yasuhiko Rust Solo?

To join by console, open it with F1 in Rust and enter client.connect 119.150.87.70:28015. Or press Launch Rust on this page, which connects you through Steam.

KeyServer tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust form.
mp1
Max players Slot count: 1.
ts8
Group limit Teams cap at 8, which is the game default.
v2633
Protocol The server runs game protocol 2633, so your game has to match it.
cs165217
Build Build 165217.
ptrak
Networking Standard game networking here, which is RakNet.
$r?
Region code No region code is 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.