Rip_Was Test Server
Key statistics
the figures behind the quote- Players now
- 0/ 10 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,940 top 71%
- Rank · 7d ago
- #16,953 ▲1013 places up
- Last wipe
- 35d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 4 Oct 2026 no hostname published
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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 128 on average | 37/300 | ▼−16−30.8% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 39/225 | ▼−4−9.1% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 92/100 | ▲+1+0.8% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 14/1000 | ▼−2−9.7% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 1/1000 | ▼−6−86.0% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 74 on average | 17/700 | ▼−27−61.7% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Rip_Was Test Server?
No gather rate appears in the name of Rip_Was Test Server. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Oxide plugins are in use. VAC is active.
Which map is played on Rip_Was Test Server?
Rip_Was Test Server uses a procedural map, which the game generates.
Population
Where does Rip_Was Test Server sit in the rankings?
For the last seven days, Rip_Was Test Server holds rank #15,940 on player hours, in the top 71% of all ranked servers.
How full is Rip_Was Test Server?
At present, Rip_Was Test Server is offline; the last sighting was 9 days 10 hours ago.
Wipe Cycle
When does Rip_Was Test Server schedule its wipes?
There are too few wipes on record for Rip_Was Test Server to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. 35 days 14 hours ago the current world was created.
Server Details
Where can Rip_Was Test Server be found?
No region is published by Rip_Was Test Server. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 91.8.202.37:28015 is its address.
What Rust version is Rip_Was Test Server running?
The version in use at Rip_Was Test Server: Rust network protocol 2633 and build 163207, on Windows. Your game needs the same protocol to get in; Steam takes care of the update.
How reliable is Rip_Was Test Server and is it currently online?
No response from Rip_Was Test Server. It was last seen 9 days 10 hours ago. The last 7 full days give 0% uptime, 0 hours on out of 168. 4 October 2026 is when Rust Analytics first saw it.
Server Tags
What is the meaning of the tags on Rip_Was Test Server?
These tags are published by Rip_Was Test Server and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team size stays at the game default of 8; v2633 (Protocol): Protocol 2633: matching game versions are required to join; cs163207 (Build): Build 163207; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The Modded listing applies: plugins or settings change play. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Rip_Was Test Server appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature Rip_Was Test Server: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Joining the Server
What steps do I take to join Rip_Was Test Server?
The console route: start Rust, press F1, enter client.connect 91.8.202.37:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp10,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z
Game
gmrust
mp10
ts8
v2633
cs163207
ptrak
$r?
Mods and access
^o
^z
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.