Rust Data

rustdata.spaceservers176.215.170.239:28082.ipynb

Run all rust-data · live

‹ All servers

Online 176.215.170.239:28015 checked 11m ago

Siberia Classical+

monthly wipes oxide

Connect

srv = rust.server("176.215.170.239:28082")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 1 # peak 6
rank #3,135 # top 14%
last wipe 28d ago # monthly schedule
next wipe 6d 21h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
AveragePeak
0123422:0007:0016:0002:0011:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020022:0007:0016:0002:0011:0020: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
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. # The force wipe · high confidence

wipe-day peak5players, last three wipes

Coming wipes

inatkind
06d 21hThu 5 Nov, 19:00 UTCFW force wipe
134d 21hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 19:12 UTC FW28d ago 5 NaN running 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

4500 · seed 165656926
Map of Siberia Classical+
map
Procedural Map
size
4500
seed
165656926
Open on RustMaps

Server

srv.info()
address
176.215.170.239:28015
region
–
max players
50
group limit
8, the default
wipe schedule
monthly
last wipe
1 Oct 2026, 19:12 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
0Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average287/300
1Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 212 on average190/200
2[EU] Facepunch 1EU · groups of 8+ · monthly · 160 on average144/400
3[EU East] Facepunch 4EU · groups of 8+ · monthly · 160 on average114/350
4Rustopia.gg - US LargeNA · groups of 16+ · monthly · 126 on average100/200
5Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 123 on average100/125

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Siberia Classical+ rank?

Rank #3,135 on seven-day player hours for Siberia Classical+, within the top 14% of all ranked servers.

What population does Siberia Classical+ carry?

Current row: 0 players on Siberia Classical+, against 50 slots. Over the last seven days it averaged 1 players and peaked at 6. Peak hour in the last 48 hours: 22:00 UTC, mean 4 players.

Server facts

How well does Siberia Classical+ perform?

Averaged over 48 hours: 132 server fps, never under 106. Buildings, deployables and all else in the world took the count as high as 123,436 entities. The memory field tops out at 4,043 MB. What players call lag is these two fields together: low fps and a rising entity count.

What Rust version does Siberia Classical+ run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Siberia Classical+. Steam updates your game for you, but the protocol must match to join.

Is Siberia Classical+ up, and what does its uptime show?

Siberia Classical+ reports itself online at the current refresh. The uptime it reports puts the last restart about 19 hours ago. Over the last 7 full days the hours up number 129 of 168, 77%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is Siberia Classical+ hosted?

No region is published by Siberia Classical+. Rust Data does not look up where the machine stands; it shows where a server says it is. 176.215.170.239:28015 is its address.

Rules, settings, map

Which rules apply on Siberia Classical+, and what settings?

The name Siberia Classical+ carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. The server browser lists it under Community. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

What is the map on Siberia Classical+?

Siberia Classical+ runs a procedural map of size 4,500 with seed 165656926, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Siberia Classical+ wipe, and how often?

Once a month Siberia Classical+ wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 28 days 2 hours ago. Its tags carry a monthly wipe schedule.

On Siberia Classical+, what happens on wipe day?

Recent wipes averaged 5 players at their peak. The crowd on the latest wipe topped out 21 hours after it began.

Lists and tags

Where does Siberia Classical+ appear among Rust Data lists and filters?

These Rust Data lists include Siberia Classical+: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

How should you read the server tags on Siberia Classical+?

Read by the game's server browser, the tags Siberia Classical+ publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Runs on Oxide (uMod) for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to Siberia Classical+?

Enter client.connect 176.215.170.239: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 mp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players 50 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Wipes follow the monthly force wipe from Facepunch.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.

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 89,192 players 11,830 servers online