Rust Data

rustdata.spaceservers162.43.37.158:29015.ipynb

Run all rust-data · live

‹ All servers

Online 162.43.37.158:28015 checked 9m ago

yubisake fingers

Connect

srv = rust.server("162.43.37.158:29015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/5 # 0% full
7-day average 0 # peak –
rank #15,341 # top 69%
last wipe 20d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123407:0016:0001:0010:0020:0005:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040007:0016:0001:0010:0020:0005: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 17 Sep. 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap19.3 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 8 OctSat 19 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 8 Oct, 21:23 UTC20d ago 0 NaN running 0
1 Sat 19 Sep, 14:26 UTC39d ago 2 halved by day 1 19.3 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

1500 · seed 34567
Map of yubisake fingers
map
Procedural Map
size
1500
seed
34567
Open on RustMaps

Server

srv.info()
address
162.43.37.158:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
8 Oct 2026, 21:23 UTC
hostname
–
first seen
13 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 537 on average199/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average185/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average14/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 281 on average16/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average18/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average101/200

Quick answers

From the figures on this page.

Player counts

What position does yubisake fingers take in the server rankings?

Rank #15,341 on seven-day player hours for yubisake fingers, within the top 69% of all ranked servers.

How many players does yubisake fingers hold at once?

yubisake fingers reports 0 players at this refresh, with 5 slots configured. Over the last seven days it averaged 0 players.

Server facts

What does performance look like on yubisake fingers?

Averaged over 48 hours: 229 server fps, never under 135. Buildings, deployables and all else in the world took the count as high as 7,157 entities. The memory field tops out at 1,432 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on yubisake fingers?

Version Rust network protocol 2634 and build 167781 on Linux is reported by yubisake fingers. Joining needs the same protocol on your game; Steam handles the update.

How reliable is yubisake fingers, and is it up?

The current sample puts yubisake fingers online. The uptime it reports puts the last restart about 11 days 10 hours ago. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.

Where does yubisake fingers sit?

For yubisake fingers, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 162.43.37.158:28015 is its address.

Map and rules

Which rules apply on yubisake fingers, and what settings?

No gather rate appears in the name: yubisake fingers. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has yubisake fingers selected?

yubisake fingers runs a procedural map of size 1,500 with seed 34567, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does yubisake fingers wipe, and how often?

The record for yubisake fingers holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 20 days 9 hours ago.

On yubisake fingers, what happens on wipe day?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 1.

Tags, lists

Where does yubisake fingers appear among Rust Data lists and filters?

The Rust Data lists that yubisake fingers fits are: Rust community servers, unfiltered. 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.

How should you read the server tags on yubisake fingers?

The game's server browser reads these tags from yubisake fingers: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way to join yubisake fingers?

In Rust, F1 opens the console: type client.connect 162.43.37.158:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp5
Max players The server lists 5 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build Build number: 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

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 35,735 players 11,617 servers online