RUST METRICSFlight deck · live data
Data live Servers11,697 Players60,803 Populated3,467 Fresh wipes 3 h115 Scan5 min
‹ All servers134.19.129.129:28015
Online Full Queue Fresh wipe Wipe due No query

SiberianServer2026

Online 134.19.129.129:28015 checked 6m ago

biweekly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Wed 09:00 UTC
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 136 SERVER FPS

Server fps

48 h low 94 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 89,147 ×1000

Entities

48 h range 82,286–90,623 · memory 1,520 MB
1239 ET SINCE RESTART 01:59

Uptime

1 h 59 min since its last restart, at the last reading
7-day average0peak 1
Rank#9,682top 44%
Last wipe23h agobiweekly schedule
Next wipe8d 7hThu 5 Nov, 19:00 UTC FW
Memory1,520MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75112:0021:0006:0015:0000:0009:00Wiped Tue 27 Oct, 11:17 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
05010015020012:0021:0006:0015:0000:0009:00Wiped Tue 27 Oct, 11:17 UTCWIPE

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.

REC 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 8d 7h. The force wipe · high confidence

usual gap5.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak5players, last three wipes
crowd held50%else halves by day 3

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 7hFW
  2. WPT 2Tue 10 Nov, 11:17 UTC13d 0h
  3. WPT 3Tue 24 Nov, 11:17 UTC27d 0h
  4. WPT 4Thu 3 Dec, 19:00 UTC36d 7hFW
  5. WPT 5Tue 8 Dec, 11:17 UTC41d 0h

The first 48 hours of its last wipes

Thu 8 OctWed 7 OctFri 2 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 11:17 UTC23h ago – – running 0
Thu 8 Oct, 13:06 UTC19d ago 4 halved by day 3 18.9 days 0
Wed 7 Oct, 23:07 UTC20d ago 4 – 0.6 days 0
Fri 2 Oct, 10:26 UTC26d ago 6 held half 5.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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on SiberianServer2026 when wipe day comes?

An average of 5 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 6 hours in. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. It fell below half by day 3 when it didn't.

What wipe timing does SiberianServer2026 follow?

Its tag guides the prediction: too few of SiberianServer2026's wipes are on record to confirm its schedule. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world it runs now was made 23 hours ago. A wipe schedule of every two weeks is published in its tags.

Lists and filters

How should you read the tags on SiberianServer2026?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): Plugin framework in use: Oxide (uMod); WA (West Asia): Its browser listing: West Asia from SiberianServer2026. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show SiberianServer2026?

These Rust Metrics lists carry SiberianServer2026: Rust community servers: live readings and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.

Occupancy

Where does SiberianServer2026 sit in the rankings?

Ranking for SiberianServer2026: #9,682 on seven-day player hours, top 44% of all ranked servers.

What is the population on SiberianServer2026?

Current headcount on SiberianServer2026: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 12:00 UTC, 0 players on average.

Operator and location

Where does SiberianServer2026 sit?

No region tag on SiberianServer2026. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 134.19.129.129:28015.

What Rust version is SiberianServer2026 on?

Rust network protocol 2635 and build 168909 on Windows is the build SiberianServer2026 runs. Matching protocol is required to join. Let Steam update your game.

Is performance on SiberianServer2026 within range?

Over the last 48 hours the average was 135 server fps; the floor was 94. Peak entity count: 90,623. Buildings, deployables and all else included. Reading: 1,963 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on SiberianServer2026, and is it online?

SiberianServer2026 reports online. Status: normal. Reading: uptime. About 1 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does SiberianServer2026 enforce, and what are its settings?

Check: gather rate. The name SiberianServer2026 does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: plugins. It runs Oxide of them. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. VAC is on. That is Valve's anti-cheat.

What map is SiberianServer2026 on?

Size 4,000 and seed 1380347505: the game generates the procedural map on SiberianServer2026 from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join SiberianServer2026?

To join: start Rust, press F1 and type client.connect 134.19.129.129:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^b,^v,WA,gmvanilla,cs168909,ts8,^o

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

^b
Biweekly Check: wipe cycle. Every two weeks.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).

Region

WA
West Asia Its browser listing: West Asia.

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.