SiberianServer2026
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 12m ago · 134.19.129.129:28015
Abstract
We describe the public Rust server SiberianServer2026, reached at 134.19.129.129:28015. At the last check it held 0 of 100 places, against a seven-day mean of 0 and a peak of 11. It ranks #9,226 of all servers, the top 42%. It last wiped 9h ago on a published biweekly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsbiweekly wipes vanilla oxide
1Summary statistics
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.
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).
4Rank
The server stands in the top 42% 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.
5Wipes
5.1Schedule: from its schedule tag
The next wipe is expected Thursday 5 November, 19:00 UTC, in 8d 22h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 5.5 days | between real wipes |
| On rhythm | 33% | of its recent wipes |
| Wipe-day peak | 5 | players, last three wipes |
| Crowd held | 50% | else halves by day 3 |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 8d 22h | force wipefw |
| Tue 10 Nov, 11:17 | 13d 14h | its own schedule |
| Tue 24 Nov, 11:17 | 27d 14h | its own schedule |
| Thu 3 Dec, 19:00 | 36d 22h | force wipefw |
| Tue 8 Dec, 11:17 | 41d 14h | its own schedule |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Tue 27 Oct, 11:179h ago | – | – | running | 0 |
| Thu 8 Oct, 13:0619d ago | 4 | – | – | 0 |
| Wed 7 Oct, 23:0719d ago | 4 | – | 0.6 d | 0 |
| Fri 2 Oct, 10:2625d ago | 6 | held half | 5.5 d | 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. 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
| 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 |
| Map | Procedural Map |
| Size | 4000 |
| Seed | 1380347505 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are busiest community rust servers [2], live vanilla server list [3] and predicted wipe schedule [4].
| Server | Players |
|---|---|
| Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average | 226/300 |
| Rustafied.com - EU Medium - LargeEU · groups of 16+ · biweekly · 157 on average | 100/150 |
| Rustopia.gg - US MediumNA · groups of 12+ · biweekly · 120 on average | 50/200 |
| Rusty Moose |US Biweekly|NA · groups of 12+ · biweekly · 97 on average | 20/200 |
| Rustoria.co - SEA MediumEA · groups of 16+ · biweekly · 82 on average | 21/200 |
| Rustoria.co - US Medium PremiumNA · groups of 12+ · biweekly · 56 on average | 30/200 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1Is the performance of SiberianServer2026 smooth?
Over the past 48 hours, it ran at an average of 136 server fps, with a low of 94. Buildings, deployables and all other world objects counted together reached a maximum of 90,623 entities. Memory use peaked at 1,963 MB. Players experience lag when fps is low and the entity count is rising.
A.2What location does SiberianServer2026 have?
No region is published by SiberianServer2026. Rust Statistics does not look up the machine's location; it shows where the server says it is. 134.19.129.129:28015 is its address.
A.3How reliable is SiberianServer2026, and is it currently online?
SiberianServer2026 is online at this time. The uptime it reports indicates a restart about 2 hours ago. The server was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.
A.4What version of Rust is run on SiberianServer2026?
The version of Rust on SiberianServer2026 is network protocol 2635 and build 168909, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.
Wipe schedule
A.5When are wipes carried out on SiberianServer2026?
The prediction follows the tag, as SiberianServer2026's recorded wipes are too few to confirm its schedule. This server's next wipe coincides with the force wipe on Thursday 5 November at 19:00 UTC, which affects all Rust servers. 9 hours have passed since the current world was generated. A fortnightly wipe schedule appears in its tags.
A.6What happens on SiberianServer2026 when wipe day arrives?
The average busiest point of recent wipes was 5 players. The peak on the latest wipe came 6 hours after it began. Half the peak was sustained until the next wipe in 50% of recent wipes. In the other cases, the population fell below half by day 3.
Population
A.7What is the rank of SiberianServer2026 among Rust servers?
The seven-day player-hours ranking puts SiberianServer2026 at #9,226, within the top 42% of ranked servers.
A.8How would you characterise the player activity on SiberianServer2026?
On SiberianServer2026, 0 of the 100 slots are occupied at present. Over the last week the count averages 0 players and reaches 1 at its height. The busiest hour of the last 48 is 12:00 UTC, averaging 0 players.
Tags, lists
A.9How should the tags on SiberianServer2026 be interpreted?
gmvanilla (Game mode): This is survival in its vanilla form; mp100 (Max players): The slot count is 100; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Your game must run protocol 2635 to connect; 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): The region code is unset; ^b (Biweekly): Every two weeks the server wipes; ^v (Vanilla): This is the game as Facepunch ships it, with rates, kits and rules unaltered; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; WA (West Asia): In the server browser it is filed under West Asia: these are the tags SiberianServer2026 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 SiberianServer2026 be found among the Rust Statistics lists and filters?
The Rust Statistics lists that SiberianServer2026 fits are: Rust community servers, measured and Vanilla Rust servers. These filters on the server list return it: 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.
Settings and map
A.11Which settings and rules are in force on SiberianServer2026?
The name of SiberianServer2026 states no gather rate. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Players may raid and fight one another. The server browser lists it under Community. Oxide plugins are running. The server's own description is vanilla: this is the game as Facepunch ships it, with rates, kits and rules unaltered. The server has VAC on, Valve's anti-cheat.
A.12What is the map for SiberianServer2026?
Generated by the game from seed 1380347505, the procedural map on SiberianServer2026 measures 4,000. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
Connection
A.13How do you connect to SiberianServer2026?
Press F1 inside Rust to open the console and enter client.connect 134.19.129.129: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 mp100,ptrak,$r?,v2635,^b,^v,WA,gmvanilla,cs168909,ts8,^o.
| Tag | Meaning |
|---|---|
| Game | |
gmvanilla | Game mode. This is survival in its vanilla form. |
mp100 | Max players. The slot count is 100. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2635 | Protocol. Your game must run protocol 2635 to connect. |
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. The region code is unset. |
| Wipe schedule | |
^b | Biweekly. Every two weeks the server wipes. |
| Difficulty | |
^v | Vanilla. This is the game as Facepunch ships it, with rates, kits and rules unaltered. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
| Region | |
WA | West Asia. In the server browser it is filed under 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.
Appendix CAbout this server, in its own words
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
- [3]Rust Statistics. Live vanilla server list. ruststatistics.org/top-vanilla-rust-servers.
- [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.