An entry in the registerNo. 3,214
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training
Online NA 104.128.58.16:28055 checked 9m ago
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training is a Rust server in North America. At the last count it had 2 players of a possible 50; over the past week it averaged 1, with a peak of 5. It stands at No. 3,214 of the ranked servers, the top 14%, and No. 532 in North America. It last wiped 7d ago, on a monthly schedule, and the next wipe is expected on Thursday 5 November, with the force wipe. Its own tags class it as modded, oxide.
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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.
§ 3Standingthe rank, daily · 1 is best
Top 14% of all ranked servers, top 29% in NA. Ranked on player hours over the last seven days.
§ 4The wipe scheduleforce wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. The force wipe · high confidence
between real wipes
players, last three wipes
else halves by day 2
| Date, UTC | Hence |
|---|---|
| Thu 5 Nov, 19:00 FW | 7d 19h |
| Thu 3 Dec, 19:00 FW | 35d 19h |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 0 hours in.
§ 5The record of wipesnewest first
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 05:02 UTC7d ago | 3 | – | running | 2 |
| Thu 1 Oct, 18:23 UTC FW27d ago | 5 | halved by day 2 | 19.4 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.
§ 6In its own wordsas the server describes itself
No Killing/Raiding/Griefing/Trespassing! Join our Discord for the full set of rules: Discord.gg/v24Tx3x2dw Plugins include: Raidable Bases Train Heist Event Plane Crash Event Heli Refuel Event Remover Tool Backpacks Vehicle License Personal Attack Heli
§ 7Similar serversthe same kind of game, then region, group limit, rate and wipes
- 1 [NA] Willjum's Casual Solo/Duo Monthly18/175 NA · groups of 8+ · monthly · 15 on average
- 2 Hempville 420 No Kos Low Decay / Limited PvP9/90 NA · groups of 8+ · monthly · 7 on average
- 3 Made in Quebec & France! QC FR EN (Website 9 Languages)2/1000 NA · groups of 8+ · monthly · 4 on average
- 4 Testing Grounds3/15 NA · groups of 8+ · monthly · 2 on average
- 5 Apocrypha-Linux | PvE | PvP0/50 NA · groups of 20+ · monthly · 1 on average
- 6 Pine Hosting - Rust Server0/50 NA · groups of 8+ · monthly · 1 on average
§ 8Questions answeredfrom the figures in this entry
The record
On which Rust version does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training operate?
The server Save Ferrous PvE - No Decay/Raidable Bases/Events/Training is on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must be on the same protocol; Steam handles the update.
How reliable is Save Ferrous PvE - No Decay/Raidable Bases/Events/Training, and is it online now?
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training currently answers as online. The uptime it reports puts the last restart at about 11 hours ago. The records show 100% uptime over the last 7 full days: 168 of 168 hours up. Rust Server Stats records a first sighting on 13 September 2026.
How does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training perform?
The records show an average of 101 server fps over 48 hours, never below 73. The entity count reached 97,463: buildings, deployables and all else in the world. Up to 3,658 MB of memory was used. Lag, as players meet it, comes from low fps and an entity count on the rise.
What is the location of Save Ferrous PvE - No Decay/Raidable Bases/Events/Training?
In North America, Save Ferrous PvE - No Decay/Raidable Bases/Events/Training lists itself with the NA tag. The location Rust Server Stats shows is the one a server states; the machine's own location is not looked up. 104.128.58.16:28055 — that is the address.
Rules, settings, map
What map does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training put players on?
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training runs a procedural map, generated by the game, of size 4,096 with seed 1337. RustMaps can display it from this page, since equal size and seed yield the same map. Map name, as listed: Custom Map.
What settings and rules does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training run?
Nothing in the name of Save Ferrous PvE - No Decay/Raidable Bases/Events/Training gives a gather rate. The group limit is 8 players, the game's default. Play is survival, gather, build and raid: the standard game. Raiding and fighting other players are allowed. It sits in the Modded section, with plugins or settings that change play. The plugin set is Oxide. VAC is enabled: Valve's anti-cheat.
Player record
How full does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training get?
At the latest count Save Ferrous PvE - No Decay/Raidable Bases/Events/Training has 2 players, with 50 slots in total. Averaged across seven days, 1 players; the peak reached 5. At 00:00 UTC, over the last 48 hours, the mean was 3 players, the highest of any hour.
What position does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training hold among Rust servers?
For seven-day player hours Save Ferrous PvE - No Decay/Raidable Bases/Events/Training is #3,214 overall and #532 in North America, in the top 14% of ranked servers.
The tags and lists
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training sits in which Rust Server Stats lists and filters?
These are the Rust Server Stats lists that include Save Ferrous PvE - No Decay/Raidable Bases/Events/Training: Modded Rust servers and North America: server records. On the server list it comes up under these filters: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.
Which meanings attach to the tags on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training?
The game's server browser reads the tags Save Ferrous PvE - No Decay/Raidable Bases/Events/Training publishes: gmvanilla (Game mode): Vanilla rules, survival play; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default applies: 8 per team; v2635 (Protocol): Join only on protocol 2635; other versions cannot connect; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries it, the standard layer for the game; $r? (Region code): The region code is not set; ^m (Monthly): One wipe a month, alongside the force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded, because settings or plugins alter the game; NA (North America): The server browser files it under North America. The tags also carry its current players, its queue and the date its world was made. These appear at the top of this page.
Wipe schedule
What happens on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training when wipe day arrives?
Averaged over recent wipes, the crowd reached 4 at its busiest. 0 hours after the latest wipe, the crowd peaked. The crowd held above half the peak until the next wipe in 0% of recent wipes. By day 2, in the wipes that did not, the crowd fell below half.
When does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training wipe?
Once a month, with the force wipe, Save Ferrous PvE - No Decay/Raidable Bases/Events/Training wipes. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers are wiped. The world now in play was generated 7 days 18 hours ago. Its tags carry a monthly wipe schedule.
Connection
How does one connect to Save Ferrous PvE - No Decay/Raidable Bases/Events/Training?
Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 104.128.58.16:28055.