Station XX-13264 · no signal
Rip_Was Test Server
Offline 217.235.33.249:28015 checked 41d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,264
- no region published
- Last wipe
- 50d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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?
Rip_Was Test Server uses a procedural map, which the game generates.
Which settings and rules apply on Rip_Was Test Server?
You will find no gather rate in the name of Rip_Was Test Server. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on Rip_Was Test Server?
A reading taken now finds Rip_Was Test Server offline; the most recent activity was 41 days 6 hours ago.
How does Rip_Was Test Server rank against other Rust servers?
Over the last seven days, Rip_Was Test Server recorded enough player hours to reach #13,264 worldwide, placing it in the top – of all ranked servers.
Server details
How reliably does Rip_Was Test Server stay online?
No contact with Rip_Was Test Server right now, and the last recorded contact was 41 days 6 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does Rip_Was Test Server run from?
No region is published by Rip_Was Test Server. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 217.235.33.249:28015 is the address it uses.
What build of Rust does Rip_Was Test Server use?
Rip_Was Test Server is running Rust network protocol 2633 and build 163207 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
On what timetable does Rip_Was Test Server run its wipes?
Too few wipes of Rip_Was Test Server are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 50 days 9 hours.
Server tags
What do the server tags on Rip_Was Test Server mean?
These are the tags Rip_Was Test Server publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs163207 (Build): Game build: 163207; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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?
These Rust Server Trends lists include Rip_Was Test Server: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto Rip_Was Test Server?
Enter client.connect 217.235.33.249:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.