Rip_Was Test Server
Key statistics
the figures behind the quote- Players now
- 1/ 10 10% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #13,264 no region published
- Rank · 7d ago
- – not ranked a week ago
- 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
- 1 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 13 Sep 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 bestWipe 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 | 71/300 | ▼−40−36.3% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 55/225 | ▼−26−32.0% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 92/100 | ▲+2+1.8% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 85 on average | 23/1000 | ▼−22−49.0% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 6/1000 | ▼−14−69.6% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 18/700 | ▼−49−73.0% |
Quick answers
from the figures on this pageMap and Rules
How is Rip_Was Test Server configured in terms of rules and settings?
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. survival is the mode, 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. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on Rip_Was Test Server?
The game generates the procedural map on Rip_Was Test Server.
Player Count
What is the rank of Rip_Was Test Server?
For the last seven days, Rip_Was Test Server holds rank #13,264 on player hours, in the top – of all ranked servers.
How full is Rip_Was Test Server?
At present, Rip_Was Test Server is offline; the last sighting was 26 days 12 hours ago.
Wipe Cycle
When does Rip_Was Test Server schedule its wipes?
The record holds too few of Rip_Was Test Server's wipes to establish its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. 35 days 16 hours ago the current world was created.
Server Info
What is the location of Rip_Was Test Server?
For Rip_Was Test Server, no region is published. Rust Analytics reports the location a server claims, not the machine's actual location. 217.235.33.249:28015 is its address.
Rip_Was Test Server runs which version of Rust?
The version in use at Rip_Was Test Server: Rust network protocol 2633 and build 163207, on Windows. The protocol has to match for you to join, and Steam applies that update.
Is Rip_Was Test Server up, and how consistent is its uptime?
No response from Rip_Was Test Server. It was last seen 26 days 12 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. The earliest Rust Analytics saw it was 13 September 2026.
Tags & Filters
How should you interpret the tags on Rip_Was Test Server?
Published by Rip_Was Test Server for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp10 (Max players): It holds 10 slots; ts8 (Group limit): 8 per team: the default setting, unchanged; v2633 (Protocol): To join, your game needs protocol 2633; cs163207 (Build): Game build: 163207; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does Rip_Was Test Server show up in Rust Analytics lists and filters?
On Rust Analytics, Rip_Was Test Server matches these lists: 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.
Connection
What is the process to join Rip_Was Test Server?
Type client.connect 217.235.33.249:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
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.