Rust Data

rustdata.spaceservers157.85.95.103:24840.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.95.103:24839 checked 8m ago

Yarrak01

moddedoxide

Connect

srv = rust.server("157.85.95.103:24840")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020020:0005:0014:0023:0008:0017:00

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, measured since 10 Oct. 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
15k10k15k20k10 Oct13 Oct17 Oct20 Oct24 Oct27 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.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 13 OctSun 11 OctSat 10 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 13 Oct, 12:40 UTC14d ago 2 NaN running 2
1 Sun 11 Oct, 11:06 UTC16d ago 3 held half 2.1 days 1
2 Sat 10 Oct, 14:01 UTC17d ago 3 NaN 0.9 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.

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

Map

3500 · seed 4413
Map of Yarrak01
map
Procedural Map
size
3500
seed
4413
Open on RustMaps

Server

srv.info()
address
157.85.95.103:24839
region
–
max players
40
group limit
8, the default
wipe schedule
–
last wipe
13 Oct 2026, 13:03 UTC
hostname
–
first seen
10 Oct 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 · 163 on average208/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 127 on average134/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 111 on average187/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average34/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 85 on average191/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average65/1000

Quick answers

From the figures on this page.

Population data

How does Yarrak01 compare in the rankings?

Player hours over seven days put Yarrak01 at #13,510, in the top 61% of the ranked set.

How many players does Yarrak01 hold at once?

Yarrak01 reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players and peaked at 1.

Server data

How smoothly does Yarrak01 run?

The 48-hour average is 116 server fps, with a low of 61. Entity numbers reached 65,851, and that includes buildings, deployables and the rest. A high of 4,576 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is Yarrak01 on?

Rust network protocol 2635 and build 167781 on Linux is what Yarrak01 runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is Yarrak01, and is it online now?

The current sample puts Yarrak01 online. A restart about 3 days 4 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 10 October 2026.

In which location is Yarrak01 hosted?

There is no region published for Yarrak01. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.95.103:24839 is its address.

Rules, settings, map

Which rules apply on Yarrak01, and what settings?

The name Yarrak01 carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on Yarrak01?

Size 3,500, seed 4413: the procedural map on Yarrak01, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does Yarrak01 wipe, and on what schedule?

Irregular wipe times on Yarrak01 leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 14 days 6 hours ago.

On Yarrak01, what happens on wipe day?

The average peak over recent wipes is 3 players. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Tags and filters

Which Rust Data filters and lists contain Yarrak01?

These Rust Data lists include Yarrak01: 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 Yarrak01 hold?

The game's server browser reads these tags from Yarrak01: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): Slot count: 40; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

What is the way to join Yarrak01?

Enter client.connect 157.85.95.103:24839 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 mp40,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players Slot count: 40.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs167781
Build Recorded game build: 167781.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 94,650 players 11,876 servers online