xer0 Solo Rust
ruststatistics.org · independent, not affiliated with Facepunch Studios
Online · checked 1h ago · 2.25.139.14:28015
Abstract
We describe the public Rust server xer0 Solo Rust, reached at 2.25.139.14:28015. At the last check it held 0 of 5 places, against a seven-day mean of 0 and a peak of 11. It ranks #8,533 of all servers, the top 38%. It last wiped 2d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsmonthly wipes modded oxide pve
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 38% 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: force wipes only
The next wipe is expected Thursday 5 November, 19:00 UTC, in 8d 0h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Usual gap | 2 days | between real wipes |
| On rhythm | 29% | of its recent wipes |
| Wipe-day peak | 1 | players, last three wipes |
| Crowd held | 33% | else halves by day 2 |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 8d 0h | force wipefw |
| Thu 3 Dec, 19:00 | 36d 0h | force wipefw |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Sun 25 Oct, 18:472d ago | 1 | – | running | 0 |
| Sun 25 Oct, 01:163d ago | 1 | – | 0.7 d | 0 |
| Sat 17 Oct, 03:4511d ago | 1 | halved by day 2 | 7.9 d | 0 |
| Thu 15 Oct, 02:5313d ago | 1 | held half | 2 d | 0 |
| Fri 9 Oct, 01:4419d ago | 1 | halved by day 2 | 6 d | 0 |
| Wed 7 Oct, 02:1021d ago | 1 | – | 2 d | 0 |
| Sat 3 Oct, 18:4125d ago | 1 | held half | 3.3 d | 0 |
| Fri 2 Oct, 05:3226d ago | 1 | – | 1.5 d | 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
| Address | 2.25.139.14:28015 |
|---|---|
| Region | – |
| Max players | 5 |
| Group limit | 8, the default |
| Wipe schedule | monthly |
| Last wipe | 25 Oct 2026, 18:47 UTC |
| Hostname | – |
| First seen | 19 Sep 2026 |
| Map | Procedural Map |
| Size | 1900 |
| Seed | 1293201566 |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2], pve wipes and settings [3] and Rust wipe forecast [4].
| Server | Players |
|---|---|
| [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 52 on average | 45/300 |
| [US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 51 on average | 40/200 |
| [US] RustEZ Survival PvE | No Decay | No Raiding | No KillingNA · groups of 8+ · monthly · 39 on average | 32/200 |
| 1[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 35 on average | 45/200 |
| [坚果PVE]原倍养老/打怪升级/合成强化/召唤副本EA · groups of 8+ · monthly · 35 on average | 35/100 |
| Zombie Land PVE Monthly | Raids | Skills | Custom MapsNA · groups of 14+ · monthly · 34 on average | 23/100 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1Does xer0 Solo Rust perform well?
Over the past 48 hours, it ran at an average of 215 server fps, with a low of 111. Buildings, deployables and all other world objects counted together reached a maximum of 17,089 entities. Memory use peaked at 1,571 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.
A.2In which location is xer0 Solo Rust based?
No region is published by xer0 Solo Rust. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 2.25.139.14:28015 is its address.
A.3What is the reliability of xer0 Solo Rust, and is it online?
xer0 Solo Rust is online at this time. Based on the uptime it reports, the last restart occurred about 2 days 21 hours ago. Of the 168 hours in the last 7 full days, 168 were served, an availability of 100%. Its first appearance in Rust Statistics's records is 19 September 2026.
A.4What version of Rust is run on xer0 Solo Rust?
xer0 Solo Rust is running Rust network protocol 2635 and build 168909 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe timing
A.5What schedule does xer0 Solo Rust follow for wipes?
The only wipe for xer0 Solo Rust is the monthly force wipe. This server's next wipe coincides with the force wipe on Thursday 5 November at 19:00 UTC, which affects all Rust servers. The world currently in use was created 2 days 23 hours ago. According to its tags, wipes happen once a month.
A.6How would you describe wipe day on xer0 Solo Rust?
Recent wipes saw an average peak of 1 players. The crowd reached its maximum 0 hours after the latest wipe. Half the peak was sustained until the next wipe in 33% of recent wipes. In the other cases, the population fell below half by day 2.
Population
A.7How does xer0 Solo Rust compare with other Rust servers in the rankings?
Ranked by player hours across seven days, xer0 Solo Rust holds #8,533, in the top 38% of all ranked servers.
A.8How would you characterise the player activity on xer0 Solo Rust?
The current population of xer0 Solo Rust is 0, drawn from 5 slots. Averaged over the last seven days: 0 players; the same period peaks at 1.
Tags and filters
A.9How should the tags on xer0 Solo Rust be interpreted?
Tags from xer0 Solo Rust, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp5 (Max players): 5 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^m (Monthly): A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe; ^p (PvE): The threat is the world, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.
A.10Where can xer0 Solo Rust be found among the Rust Statistics lists and filters?
The Rust Statistics lists that xer0 Solo Rust fits are: Modded Rust servers and Rust PvE servers: live list. These filters on the server list return it: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 3 days.
Settings and map
A.11Under what rules and settings does xer0 Solo Rust operate?
Its name carries no gather rate for xer0 Solo Rust. No cap is given beyond the game's default of 8 players per group. The mode is pve, which means no player-versus-player fighting. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.
A.12On which map does xer0 Solo Rust take place?
The game generates xer0 Solo Rust's procedural map at size 1,900, from seed 1293201566. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.
How to join
A.13What steps are required to join xer0 Solo Rust?
Press F1 inside Rust to open the console and enter client.connect 2.25.139.14: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 mp5,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp5 | Max players. 5 slots are available. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. The game build is 168909. |
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 | |
^m | Monthly. A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe. |
| Gameplay | |
^p | PvE. The threat is the world, not other players. |
| Mods and access | |
^o | Oxide. The plugin framework in use is Oxide (uMod). |
^z | Modded. The game is altered by plugins or settings, so it is listed as Modded. |
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]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Pve wipes and settings. ruststatistics.org/top-rust-pve-servers.
- [4]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.