Rust StatisticsWorking papers on every public Rust server · 83,167 players now

Siberia Classical+

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 15m ago · 176.215.170.239:28015

Abstract

We describe the public Rust server Siberia Classical+, reached at 176.215.170.239:28015. At the last check it held 1 of 50 places, against a seven-day mean of 1 and a peak of 61. It ranks #3,161 of all servers, the top 14%. It last wiped 27d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmonthly wipes oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/502% full
In the queue0no queue
Seven-day mean1peak 6, 48 h peak 6
Rank2#3,161top 14%
Last wipe27d agomonthly schedule
Next wipe37d 4hThu 5 Nov, 19:00 UTCfw

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
0246815:0000:0009:0019:0004:0013:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020015:0000:0009:0019:0004:0013:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 14% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe (high confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak5players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Thu 5 Nov, 19:007d 4hforce wipefw
Thu 3 Dec, 19:0035d 4hforce wipefw
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 5, 21 hours in.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 19:12fw27d ago 5 – 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Siberia Classical+
Figure 5: The map: Procedural Map, size 4500, seed 165656926. Open on RustMaps.
Table 5: The server's published settings.
Address176.215.170.239:28015
Region–
Max players50
Group limit8, the default
Wipe schedulemonthly
Last wipe1 Oct 2026, 19:12 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4500
Seed165656926

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and next Rust wipe times [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average422/475
Rusty Moose |EU Monthly|EU · groups of 12+ · monthly · 215 on average273/300
[EU East] Facepunch 4EU · groups of 8+ · monthly · 168 on average114/350
[EU] Facepunch 1EU · groups of 8+ · monthly · 161 on average170/400
Rustopia.gg - US LargeNA · groups of 16+ · monthly · 128 on average58/200
Rustafied.com - EU Long - LargeEU · groups of 16+ · monthly · 126 on average91/125

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of Siberia Classical+ smooth?

Over the past 48 hours, it ran at an average of 132 server fps, with a low of 110. The highest number of entities it carried was 123,436, comprising buildings, deployables and all other objects. The peak memory usage was 4,043 MB. When fps is low and entity count climbs, players feel lag.

A.2What location does Siberia Classical+ have?

A region is not published by Siberia Classical+. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 176.215.170.239:28015 is its address.

A.3What is the reliability of Siberia Classical+, and is it online?

At the present moment, Siberia Classical+ is online. The uptime it reports indicates a restart about 12 hours ago. The server was up 77% of the time over the last 7 full days, 129 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What version of Rust is run on Siberia Classical+?

Siberia Classical+ is running Rust network protocol 2635 and build 168909 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5On what cycle does Siberia Classical+ wipe?

Once a month, Siberia Classical+ wipes in line with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe occurs, and that is when every Rust server, including this one, next wipes. 27 days 19 hours have passed since the current world was generated. The tags show that the server wipes monthly.

A.6How would you describe wipe day on Siberia Classical+?

Recent wipes saw an average peak of 5 players. The crowd reached its maximum 21 hours after the latest wipe.

Player count

A.7What position does Siberia Classical+ occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Siberia Classical+ at #3,161, within the top 14% of ranked servers.

A.8How would you characterise the player activity on Siberia Classical+?

The current population of Siberia Classical+ is 1, drawn from 50 slots. The peak over seven days is 6, against an average of 1. Of the last 48 hours, the peak hour falls at 17:00 UTC, with an average of 6 players.

Tags and filters

A.9How should the tags on Siberia Classical+ be interpreted?

gmrust (Game mode): This is survival as standard Rust plays; mp50 (Max players): It offers 50 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the schedule: wipes take place once a month; ^o (Oxide): The plugin framework in use is Oxide (uMod): these are the tags Siberia Classical+ publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.10Where can Siberia Classical+ be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Siberia Classical+ fits are: Rust community servers, measured. These filters on the server list return it: 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.

Settings and map

A.11What are the settings and rules that govern Siberia Classical+?

The name of Siberia Classical+ states no gather rate. The group cap is 8 players, which is the default in the game. survival is the game mode here; gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it under Community. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on Siberia Classical+?

The game generates Siberia Classical+'s procedural map at size 4,500, from seed 165656926. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.13What is the process for joining Siberia Classical+?

Press F1 inside Rust to open the console and enter client.connect 176.215.170.239:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp50Max players. It offers 50 slots.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2635Protocol. Joining requires the same game version: protocol 2635.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.
Wipe schedule
^mMonthly. Facepunch's force wipe sets the schedule: wipes take place once a month.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.