Station XX-11346 · no signal
Rip_Was Test Server
Offline 91.8.202.37:28015 checked 1d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M0.0▲rising
- +0 players on the day
- 7-day average
- 1
- peak 1
- Rank
- #11,346
- top 51%
- Last wipe
- 5d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M0.0▲rising+0 players
- Sharpest hour
- +0into Tue 21:00 UTC
- Peak · 48 h
- 1most players in any hour
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 51% 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 |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 14:24 UTC5d ago | M0.0▲rising | 1 | – | running | 0 |
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 pageServer rules
Which map is running on Rip_Was Test Server?
The map on Rip_Was Test Server is procedural, produced by the game.
Which settings and rules apply on Rip_Was Test Server?
The name of Rip_Was Test Server gives no gather rate. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Rip_Was Test Server right now?
Rip_Was Test Server is not responding at this moment and is offline, last seen 26 hours ago. Across seven days this server recorded an average of 1 players and a peak of 1. Averaged over the last 48 hours, the busiest hour was 21:00 UTC at 1 players.
How does Rip_Was Test Server rank against other Rust servers?
The last seven days of player hours place Rip_Was Test Server at #11,346, in the top 51% of all ranked servers.
Operator and location
How reliably does Rip_Was Test Server stay online?
As recorded now, Rip_Was Test Server is not reachable, the last contact having been 26 hours ago. It was up 2% of the time across the last 7 full days: 4 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 4 October 2026.
Where in the world is Rip_Was Test Server hosted?
A region is not published by Rip_Was Test Server. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 91.8.202.37:28015.
What build of Rust does Rip_Was Test Server use?
Rust network protocol 2635 and build 168909 on Windows is what Rip_Was Test Server runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on Rip_Was Test Server?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does Rip_Was Test Server wipe, and on which days?
Too few wipes of Rip_Was Test Server are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 5 days 9 hours.
Tags
What do the server tags on Rip_Was Test Server mean?
Tags published by Rip_Was Test Server and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Rip_Was Test Server appear?
You will find Rip_Was Test Server 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; Last wipe: In the last week.
Connecting
What steps get you onto Rip_Was Test Server?
To join, enter client.connect 91.8.202.37: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.