Rust Data

rustdata.spaceservers217.60.245.30:28028.ipynb

Run all rust-data · live

‹ All servers

Offline 217.60.245.30:28027 checked 5d ago

Snow_Test_Clean

moddedoxide

Connect

srv = rust.server("217.60.245.30:28028")
print(srv.connect_command)

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 1 # peak 2
rank #6,644 # top 30%
last wipe 6d 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, measured since 18 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
15k10k15k20k18 Oct20 Oct22 Oct24 Oct26 Oct28 Oct

Top 30% 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 gap0.5 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 22 OctTue 20 OctMon 19 Oct
00.511.52+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 Thu 22 Oct, 03:56 UTC6d ago 1 NaN running 1
1 Tue 20 Oct, 21:26 UTC8d ago 2 NaN 1.3 days 0
2 Mon 19 Oct, 11:05 UTC9d ago 1 NaN 1.4 days 0
3 Sun 18 Oct, 22:05 UTC9d ago 1 NaN 0.5 days 0
4 Sun 18 Oct, 15:09 UTC10d ago 1 NaN 0.3 days 0
5 Sun 18 Oct, 05:24 UTC10d ago 1 NaN 0.4 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

2200 · seed 1337
Map of Snow_Test_Clean
map
Procedural Map
size
2200
seed
1337
Open on RustMaps

Server

srv.info()
address
217.60.245.30:28027
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 03:56 UTC
hostname
–
first seen
18 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 · 157 on average98/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average101/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 91 on average87/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average29/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average21/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Snow_Test_Clean rank?

Over the last seven days Snow_Test_Clean sits at #6,644 on player hours, in the top 30% of ranked servers.

What population does Snow_Test_Clean carry?

Snow_Test_Clean returns no live count at this refresh, having last been seen 5 days 7 hours ago. Over the last seven days it averaged 1 players and peaked at 2.

Server data

What is the Rust version on Snow_Test_Clean?

Version Rust network protocol 2617 and build 140534 on Linux is reported by Snow_Test_Clean. Joining needs the same protocol on your game; Steam handles the update.

Is Snow_Test_Clean up, and what does its uptime show?

The latest sample has Snow_Test_Clean offline, with a last sighting 5 days 7 hours ago. Uptime of 24% across the last 7 full days: 40 hours of 168. The first row Rust Data holds for it is dated 18 October 2026.

Where does Snow_Test_Clean sit?

There is no region published for Snow_Test_Clean. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 217.60.245.30:28027.

Map and rules

What rules and settings are recorded for Snow_Test_Clean?

The name Snow_Test_Clean carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is not running; Valve's anti-cheat is off.

Which map has Snow_Test_Clean loaded?

The game generates the map on Snow_Test_Clean: procedural, size 2,200, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

On what schedule does Snow_Test_Clean wipe?

Snow_Test_Clean 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. The world it runs now was generated 6 days 17 hours ago.

On Snow_Test_Clean, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.

Tags, lists

Where does Snow_Test_Clean appear among Rust Data lists and filters?

These Rust Data lists include Snow_Test_Clean: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on Snow_Test_Clean hold?

Read by the game's server browser, the tags Snow_Test_Clean publishes are: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): 20 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2617 (Protocol): Protocol 2617 is required; a different game version cannot connect; cs140534 (Build): The server runs build 140534; 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): Plugins or settings alter the game, so it sits under Modded. 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.

Join steps

What is the way to join Snow_Test_Clean?

The manual route: launch Rust, F1, then client.connect 217.60.245.30:28027. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. You will find its website at https://free-rust.pro.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2617,gmrust,cs140534,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp20
Max players 20 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2617
Protocol Protocol 2617 is required; a different game version cannot connect.
cs140534
Build The server runs build 140534.
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 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 67,584 players 11,791 servers online