Rust Data

rustdata.spaceservers153.231.58.191:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 153.231.58.191:28015 checked 4d ago

yurusaba

moddedoxide

Connect

srv = rust.server("153.231.58.191:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/500 # 0% full
7-day average 1 # peak 1
rank #13,618 # top 61%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k21 Sep29 Sep6 Oct14 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

usual gap1.1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 17 OctSat 10 OctSat 10 Oct
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.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 17 Oct, 17:02 UTC11d ago 1 NaN running 0
1 Sat 10 Oct, 20:07 UTC18d ago 1 held half 6.9 days 1
2 Sat 10 Oct, 12:21 UTC18d ago 1 NaN 0.3 days 1
3 Fri 9 Oct, 23:56 UTC19d ago 1 NaN 0.5 days 1
4 Fri 9 Oct, 17:54 UTC19d ago 1 NaN 0.3 days 1
5 Sat 3 Oct, 01:21 UTC26d ago 1 held half 6.7 days 1
6 Thu 1 Oct, 20:27 UTC FW27d ago 1 NaN 1.2 days 1
7 Tue 22 Sep, 21:49 UTC36d ago 1 held half 8.9 days 1
8 Mon 21 Sep, 20:21 UTC37d ago 1 NaN 1.1 days 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.

display(srv.map, srv.info())

Map

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
153.231.58.191:28015
region
–
max players
500
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 20:27 UTC
hostname
–
first seen
21 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average32/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average30/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average24/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average5/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average4/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does yurusaba rank?

Rank #13,618 on seven-day player hours for yurusaba, within the top 61% of all ranked servers.

What population does yurusaba carry?

Offline now for yurusaba, with the last sample 4 days 20 hours ago. Over the last seven days it averaged 1 players and peaked at 1.

About the server

What Rust version does yurusaba run?

Version Rust network protocol 2635 and build 168909 on Windows is reported by yurusaba. Joining needs the same protocol on your game; Steam handles the update.

How reliable is yurusaba, and is it up?

Offline now for yurusaba, last seen 4 days 20 hours ago. Over the last 7 full days the hours up number 1 of 168, 1%. Its earliest recorded date in Rust Data is 21 September 2026.

In which location is yurusaba hosted?

For yurusaba, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 153.231.58.191:28015 is its address.

Map and rules

Which rules apply on yurusaba, and what settings?

No gather rate appears in the name: yurusaba. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

Wipe schedule

When does yurusaba wipe, and how often?

yurusaba wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 27 days 5 hours ago, and that is the one in play.

What is wipe day on yurusaba like?

The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags and filters

Which Rust Data filters and lists contain yurusaba?

On Rust Data, yurusaba appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on yurusaba hold?

The game's server browser reads these tags from yurusaba: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join yurusaba?

Enter client.connect 153.231.58.191:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp500
Max players The server lists 500 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 41,781 players 11,700 servers online