Online NA 104.128.58.16:28055 checked 15m ago
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training
Connect
srv = rust.server("104.128.58.16:28056")
print(srv.connect_command)Right now
srv.summary()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 14% of all ranked servers, top 28% in NA. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 21 Oct, 05:02 UTC6d ago | 3 | NaN | running | 2 |
| 1 | Thu 1 Oct, 18:23 UTC FW26d 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.
display(srv.map, srv.info())Map
4096 · seed 1337
- map
- Custom Map
- size
- 4096
- seed
- 1337
Server
srv.info()- address
- 104.128.58.16:28055
- region
- NA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 21 Oct 2026, 05:02 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 | [NA] Willjum's Casual Solo/Duo Monthly | NA · groups of 8+ · monthly · 16 on average | 8/175 |
| 1 | Hempville 420 No Kos Low Decay / Limited PvP | NA · groups of 8+ · monthly · 7 on average | 11/90 |
| 2 | Made in Quebec & France! QC FR EN (Website 9 Languages) | NA · groups of 8+ · monthly · 4 on average | 4/1000 |
| 3 | Testing Grounds | NA · groups of 8+ · monthly · 2 on average | 2/15 |
| 4 | Apocrypha-Linux | PvE | PvP | NA · groups of 20+ · monthly · 1 on average | 2/50 |
| 5 | [US] Busy Adults PVP BY Chill-AXX | NA · groups of 8+ · monthly · 1 on average | 0/50 |
Quick answers
From the figures on this page.
Population
How does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training compare in the rankings?
On seven-day player hours Save Ferrous PvE - No Decay/Raidable Bases/Events/Training is #3,183 overall and #525 in North America, inside the top 14% of all ranked servers.
What population does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training carry?
Current row: 1 players on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training, against 50 slots. Over the last seven days it averaged 1 players and peaked at 5. The 48-hour sample puts the busiest hour at 23:00 UTC, averaging 4 players.
Server facts
How well does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training perform?
The 48-hour average is 91 server fps, with a low of 66. Entity numbers reached 99,609, and that includes buildings, deployables and the rest. The memory field tops out at 3,545 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training?
Rust network protocol 2635 and build 168909 on Linux is what Save Ferrous PvE - No Decay/Raidable Bases/Events/Training runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Save Ferrous PvE - No Decay/Raidable Bases/Events/Training, and is it up?
Online is the state at the latest refresh for Save Ferrous PvE - No Decay/Raidable Bases/Events/Training. The uptime it reports puts the last restart about 8 hours ago. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training sit?
With its NA tag, Save Ferrous PvE - No Decay/Raidable Bases/Events/Training lists itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 104.128.58.16:28055.
Map and rules
Which settings and rules does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training run?
No gather rate appears in the name: Save Ferrous PvE - No Decay/Raidable Bases/Events/Training. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training?
Save Ferrous PvE - No Decay/Raidable Bases/Events/Training runs a procedural map of size 4,096 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.
Wipe schedule
When does Save Ferrous PvE - No Decay/Raidable Bases/Events/Training wipe, and how often?
The only wipe Save Ferrous PvE - No Decay/Raidable Bases/Events/Training takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 6 days 15 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
What is wipe day on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training like?
Recent wipes averaged 4 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 2.
Tags, lists
Which lists on Rust Data hold Save Ferrous PvE - No Decay/Raidable Bases/Events/Training, and which filters?
The Rust Data lists that Save Ferrous PvE - No Decay/Raidable Bases/Events/Training fits are: Modded Rust servers and North America Rust servers. It appears under these filters on the server list: 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 week.
Which meanings do the tags on Save Ferrous PvE - No Decay/Raidable Bases/Events/Training hold?
Read by the game's server browser, the tags Save Ferrous PvE - No Decay/Raidable Bases/Events/Training publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings; NA (North America): The server browser files it under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join Save Ferrous PvE - No Decay/Raidable Bases/Events/Training?
Enter client.connect 104.128.58.16:28055 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.