Rip_Was Test Server
Offline 91.8.202.37:28015 checked 14h ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avg7-day peakServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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.
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 14:24 UTC4d ago | 1 | – | running | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 172/500
- 133/100
- 179/225
- 126/700
- 15/200
- 54/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Rip_Was Test Server?
At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.
How often does Rip_Was Test Server wipe, and when?
The rhythm of Rip_Was Test Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 4 days 21 hours ago.
Tag meanings
Which tags does Rip_Was Test Server carry, and what do they mean?
These are the tags Rip_Was Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Rip_Was Test Server appear in Rust Metrics lists and filters?
On Rust Metrics, Rip_Was Test Server sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Player count
What position does Rip_Was Test Server hold among Rust servers?
Player hours over seven days put Rip_Was Test Server at #11,390, in the top 51% of all ranked servers.
What is the population on Rip_Was Test Server?
Rip_Was Test Server is not responding; status offline, last seen 14 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Average at the busiest hour was 1 players, at 21:00 UTC over the last 48 hours.
Operator and location
What location is Rip_Was Test Server hosted in?
No region comes from Rip_Was Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 91.8.202.37:28015.
What Rust version is Rip_Was Test Server on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by Rip_Was Test Server. Matching protocol is required to join. Let Steam update your game.
Is Rip_Was Test Server up, and how often does it stay up?
Rip_Was Test Server reports offline. The last reading came 14 hours ago. Uptime for the last 7 full days: 4 of 168 hours, or 2%. Reading: first seen 4 October 2026, recorded by Rust Metrics.
Settings and map
What rules does Rip_Was Test Server enforce, and what are its settings?
No gather rate appears in the name: Rip_Was Test Server. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Rip_Was Test Server?
Procedural map on Rip_Was Test Server, made by the game's generator.
Join
How can you get onto Rip_Was Test Server?
Check: join. Open Rust, press F1, then enter client.connect 91.8.202.37:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.