Station XX-14312 · no signal
SUFFERING|MONTHLY[TEST]
Offline 91.214.140.157:28015 checked 40d ago
- Players now
- 0/ 200
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #14,312
- top 65%
- Last wipe
- 43d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 200 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Thu 8 Oct, 18:19 UTC43d ago | M0.0■steady | 1 | – | – | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on SUFFERING|MONTHLY[TEST]?
The map on SUFFERING|MONTHLY[TEST] is procedural, produced by the game.
Which settings and rules apply on SUFFERING|MONTHLY[TEST]?
No gather rate appears in the name of SUFFERING|MONTHLY[TEST]. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. Anti-cheat is off: VAC, from Valve.
Player counts
How many players are recorded on SUFFERING|MONTHLY[TEST] right now?
SUFFERING|MONTHLY[TEST] is not responding at this moment and is offline, last seen 40 days 10 hours ago.
How does SUFFERING|MONTHLY[TEST] rank against other Rust servers?
The last seven days of player hours place SUFFERING|MONTHLY[TEST] at #14,312, in the top 65% of all ranked servers.
Server facts
How reliably does SUFFERING|MONTHLY[TEST] stay online?
No contact with SUFFERING|MONTHLY[TEST] right now, and the last recorded contact was 40 days 10 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 2 October 2026.
Where in the world is SUFFERING|MONTHLY[TEST] hosted?
A region is not published by SUFFERING|MONTHLY[TEST]. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 91.214.140.157:28015.
What build of Rust does SUFFERING|MONTHLY[TEST] use?
Rust network protocol 2634 and build 167398 on Windows is what SUFFERING|MONTHLY[TEST] runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on SUFFERING|MONTHLY[TEST]?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does SUFFERING|MONTHLY[TEST] run its wipes?
On record so far are too few of SUFFERING|MONTHLY[TEST]'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. It has run its current world for 43 days 18 hours.
Tags
What do the server tags on SUFFERING|MONTHLY[TEST] mean?
These are the tags SUFFERING|MONTHLY[TEST] publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp200 (Max players): 200 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167398 (Build): It runs game build 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does SUFFERING|MONTHLY[TEST] appear?
You will find SUFFERING|MONTHLY[TEST] on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to SUFFERING|MONTHLY[TEST]?
To join, enter client.connect 91.214.140.157:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.