Rip_Was Test Server
Offline 91.8.202.37:28015 checked 1h ago
Measurements
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
Top 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not 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
| 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.
Quick answers
Player counts
How does Rip_Was Test Server rank against other Rust servers?
By player hours over the last seven days, Rip_Was Test Server places at #12,815, within the top 58% of ranked servers.
How busy is Rip_Was Test Server?
Rip_Was Test Server is offline at this count; we last saw it 1 hours ago. Seven days of counting give an average of 0 players and a peak of 1. Look at the last 48 hours and 20:00 UTC stands out: it averaged 0 players.
Lists and tags
What do the server tags on Rip_Was Test Server mean?
These are the tags Rip_Was Test Server publishes, as read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): The protocol is 2635; a different version will not connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Rip_Was Test Server?
These Rust Population lists include Rip_Was Test Server: Modded Rust servers, counted. These are the filters it appears under when you browse the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Wipe notes
What does wipe day look like on Rip_Was Test Server?
Across its recent wipes the busiest crowds averaged 1 players. The crowd on the latest wipe peaked 0 hours in.
What is the wipe schedule on Rip_Was Test Server?
Its rhythm cannot be told yet: too few of Rip_Was Test Server's wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. 4 days 7 hours ago the current world was made.
Settings
Which map does Rip_Was Test Server run?
A procedural map, generated by the game, is in use on Rip_Was Test Server.
What are the rules and settings on Rip_Was Test Server?
No gather rate appears in the name of Rip_Was Test Server. No limit is set beyond the standard 8 players per group. This server runs survival, gather, build and raid, as in the standard game. You can raid and fight other players here. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does Rip_Was Test Server run?
On Windows, Rip_Was Test Server runs Rust network protocol 2635 and build 168909. Your game needs the same protocol to join; Steam takes care of updating it.
Is Rip_Was Test Server online, and how reliable is it?
We last saw Rip_Was Test Server 1 hours ago, and it is offline now. Over the last 7 full days, 2 of 168 hours were online, or 1%. On 4 October 2026, Rust Population saw it for the first time.
Where is Rip_Was Test Server located?
Nothing published by Rip_Was Test Server states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 91.8.202.37:28015.
How to join
How do I join Rip_Was Test Server?
Open the console with F1 in Rust and enter client.connect 91.8.202.37:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.