Rust Data

rustdata.spaceservers88.198.59.60:25608.ipynb

Run all rust-data · live

‹ All servers

Online 88.198.59.60:25574 checked 10m ago

SnD Test

moddedoxide

Connect

srv = rust.server("88.198.59.60:25608")
print(srv.connect_command)

Right now

srv.summary()
players now 0/40 # 0% full
7-day average 0 # peak –
rank #15,268 # top 68%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020022:0007:0016:0001:0010:0019: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 68% 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 gap9.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 2

The first 48 hours of its last wipes

Fri 2 OctFri 25 SepSun 13 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 02:29 UTC27d ago 2 NaN running 0
1 Fri 25 Sep, 06:48 UTC34d ago 2 held half 6.8 days 0
2 Sun 13 Sep, 18:16 UTC46d ago 1 halved by day 2 11.5 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

3000 · seed 1
Map of SnD Test
map
Procedural Map
size
3000
seed
1
Open on RustMaps

Server

srv.info()
address
88.198.59.60:25574
region
–
max players
40
group limit
50 max
wipe schedule
–
last wipe
2 Oct 2026, 02:29 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
0ShockRust | Blue | NoLimitno group limit · 150 on average68/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average131/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 119 on average115/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average38/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 92 on average124/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average346/350

Quick answers

From the figures on this page.

Player counts

How does SnD Test compare in the rankings?

Rank #15,268 on seven-day player hours for SnD Test, within the top 68% of all ranked servers.

How many players does SnD Test hold at once?

SnD Test reports 0 players at this refresh, with 40 slots configured. Over the last seven days it averaged 0 players.

Server data

What does performance look like on SnD Test?

Averaged over 48 hours: 120 server fps, never under 6. Buildings, deployables and all else in the world took the count as high as 48,417 entities. Memory peaked at 2,069 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does SnD Test run?

Rust network protocol 2635 and build 168909 on Linux is what SnD Test runs. Steam updates your game for you, but the protocol must match to join.

Is SnD Test up, and what does its uptime show?

The current sample puts SnD Test online. The uptime it reports puts the last restart about 17 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.

Where does SnD Test sit?

No region is published by SnD Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 88.198.59.60:25574 is its address.

Rules, settings, map

Which settings and rules does SnD Test run?

You will not find a gather rate in the string SnD Test. 50 players is the maximum per group. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has SnD Test selected?

The game generates the map on SnD Test: procedural, size 3,000, seed 1. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe data

When does SnD Test wipe, and on what schedule?

SnD Test wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 27 days 18 hours ago, and that is the one in play.

What is wipe day on SnD Test like?

Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 18 hours in. Half the peak or more was held to the next wipe in 50% of recent wipes. The drop under half arrived by day 2 in the other cases.

Tags and filters

Which lists on Rust Data hold SnD Test, and which filters?

On Rust Data, SnD Test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on SnD Test hold?

Read by the game's server browser, the tags SnD Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts50 (Group limit): The team cap is 50; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join SnD Test?

In Rust, F1 opens the console: type client.connect 88.198.59.60:25574. 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 mp40,ptrak,$r?,v2635,gmrust,cs168909,ts50,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp40
Max players 40 slots in total.
ts50
Group limit The team cap is 50.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 91,106 players 11,828 servers online