Station XX-14615 · no signal
Siberia Classical-
Offline 94.231.125.242:28015 checked 35d ago
- Players now
- 1/ 50
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,615
- top 66%
- Last wipe
- 35d ago
- monthly schedule
- Next wipe
- 6d 19h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 50 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 19h. The force wipe · high confidence
- usual gap
- 3.1 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 6d 19hThu 5 Nov, 19:00 UTCFW
- 34d 19hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 24 Sep, 10:45 UTC35d ago | M0.0▲rising | 1 | – | running | 0 | |
| Wed 23 Sep, 06:29 UTC36d ago | M0.0■steady | 1 | – | 1.2 days | 1 | |
| Fri 18 Sep, 06:37 UTC41d ago | M0.0▲rising | 1 | – | – | 5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Siberia Classical-?
A procedural map runs on Siberia Classical-, generated by the game.
Which settings and rules apply on Siberia Classical-?
You will find no gather rate in the name of Siberia Classical-. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on Siberia Classical-?
A reading taken now finds Siberia Classical- offline; the most recent activity was 35 days 11 hours ago.
How does Siberia Classical- rank against other Rust servers?
The last seven days of player hours place Siberia Classical- at #14,615, in the top 66% of all ranked servers.
Server details
How reliably does Siberia Classical- stay online?
No contact with Siberia Classical- right now, and the last recorded contact was 35 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 17 September 2026.
Where in the world is Siberia Classical- hosted?
Nothing about a region comes from Siberia Classical-. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 94.231.125.242:28015.
What build of Rust does Siberia Classical- use?
On Linux, Siberia Classical- runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Siberia Classical-?
On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Siberia Classical- run its wipes?
The force wipe is the only wipe Siberia Classical- takes, once a month. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. It has run its current world for 35 days 12 hours. A monthly wipe schedule is published in its tags.
Server tags
What do the server tags on Siberia Classical- mean?
These are the tags Siberia Classical- publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): It runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^o (Oxide): Oxide (uMod) is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Siberia Classical- appear?
You will find Siberia Classical- on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: 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.
Connecting
What steps get you onto Siberia Classical-?
You can connect by pressing F1 in Rust and typing client.connect 94.231.125.242:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.