Online 134.19.129.129:28015 checked 11m ago
SiberianServer2026
Connect
srv = rust.server("134.19.129.129:28016")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 bestTop 42% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 10h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 2h | Tue 10 Nov, 11:17 UTC | wipe |
| 2 | 27d 2h | Tue 24 Nov, 11:17 UTC | wipe |
| 3 | 36d 10h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 2h | Tue 8 Dec, 11:17 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 11:17 UTC21h ago | NaN | NaN | running | 0 |
| 1 | Thu 8 Oct, 13:06 UTC19d ago | 4 | halved by day 3 | 18.9 days | 0 |
| 2 | Wed 7 Oct, 23:07 UTC20d ago | 4 | NaN | 0.6 days | 0 |
| 3 | Fri 2 Oct, 10:26 UTC25d 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.
display(srv.map, srv.info())Map
4000 · seed 1380347505
- map
- Procedural Map
- size
- 4000
- seed
- 1380347505
Server
srv.info()- address
- 134.19.129.129:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 27 Oct 2026, 11:17 UTC
- hostname
- ^
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 276 on average | 139/200 |
| 1 | Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 151 on average | 28/100 |
| 2 | Rustopia.gg - US Medium | NA · groups of 12+ · biweekly · 109 on average | 17/200 |
| 3 | Rusty Moose |US Biweekly| | NA · groups of 12+ · biweekly · 81 on average | 17/200 |
| 4 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 77 on average | 39/200 |
| 5 | Rustoria.co - US Medium Premium | NA · groups of 12+ · biweekly · 48 on average | 5/200 |
Quick answers
From the figures on this page.
Population data
How does SiberianServer2026 compare in the rankings?
Player hours over seven days put SiberianServer2026 at #9,258, in the top 42% of the ranked set.
How full does SiberianServer2026 run?
The sample now reads 0 players for SiberianServer2026, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 12:00 UTC, mean 0 players.
About the server
How well does SiberianServer2026 perform?
Server fps over the last 48 hours averages 135; the floor is 94. Buildings, deployables and all else in the world took the count as high as 90,623 entities. Memory peaked at 1,963 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does SiberianServer2026 run?
Rust network protocol 2635 and build 168909 on Windows is what SiberianServer2026 runs. The protocol has to match before you can join, and Steam does the updating.
Is SiberianServer2026 up, and what does its uptime show?
SiberianServer2026 reports itself online at the current refresh. The uptime it reports puts the last restart about 4 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 13 September 2026.
Which location does SiberianServer2026 run from?
For SiberianServer2026, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 134.19.129.129:28015 is its address.
Rules, settings, map
Which settings and rules does SiberianServer2026 run?
You will not find a gather rate in the string SiberianServer2026. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. Oxide plugins run on it. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC on.
Which map has SiberianServer2026 loaded?
The game generates the map on SiberianServer2026: procedural, size 4,000, seed 1380347505. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does SiberianServer2026 wipe, and on what schedule?
The tag sets the prediction: SiberianServer2026 has too few wipes on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 21 hours ago. A fortnightly wipe schedule is published in its tags.
On SiberianServer2026, what happens on wipe day?
The average peak over recent wipes is 5 players. Peak population on the latest wipe came 6 hours in. Half the peak or more was held to the next wipe in 50% of recent wipes. The drop under half arrived by day 3 in the other cases.
Tags and filters
Which lists on Rust Data hold SiberianServer2026, and which filters?
The Rust Data lists that SiberianServer2026 fits are: Rust community servers, unfiltered and Vanilla Rust servers. These filters bring it up on the server list: 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.
How should you read the server tags on SiberianServer2026?
These tags are published by SiberianServer2026 and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): The plugin framework in use is Oxide (uMod); WA (West Asia): The server browser files it under West Asia. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into SiberianServer2026?
In Rust, F1 opens the console: type client.connect 134.19.129.129:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.