Skip to the content
Dive report

Rip_Was Test Server

Offline 217.235.33.249:28015 checked 30d ago

moddedoxide
Drop in
1/ 10 players now 10% full
07-day averagepeak –
#13,264rankno region published
39d agolast wipeno schedule published
–next wipeno wipe seen yet

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Neighbouring dive spots

Similar servers

the same kind of game, then region, group limit, rate and wipes

From the figures on this page

Quick answers

Tags and search

Where does Rip_Was Test Server appear in Rust Going Deep lists and filters?

These Rust Going Deep lists include Rip_Was Test Server: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the tags on Rip_Was Test Server?

The server browser shows these tags for Rip_Was Test Server: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): The slot count is 10; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163207 (Build): It's on build 163207; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.

About the server

What's the location of Rip_Was Test Server?

There is no published region for Rip_Was Test Server. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. To connect, use 217.235.33.249:28015.

Is Rip_Was Test Server up, and how often does it stay online?

The server Rip_Was Test Server is not reachable at the moment; the last sighting was 30 days 14 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 13 September 2026.

What is the Rust version for Rip_Was Test Server?

The version on Rip_Was Test Server is Rust network protocol 2633 and build 163207, on Windows. The protocol must match to join; Steam will update your game.

Wipe schedule

When does Rip_Was Test Server wipe?

Rip_Was Test Server's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 39 days 18 hours ago.

Map and rules

What settings and rules have been applied to Rip_Was Test Server?

The name of Rip_Was Test Server contains no gather rate. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.

What's the map on Rip_Was Test Server?

A procedural map, generated by the game, is in play on Rip_Was Test Server.

Player count

What's the population like on Rip_Was Test Server?

Rip_Was Test Server was last seen 30 days 14 hours ago and is offline as you read this.

Where does Rip_Was Test Server sit in the rankings?

Over the last seven days, Rip_Was Test Server is #13,264 by player hours, among the top – of all ranked servers.

Join info

What's the way to join Rip_Was Test Server?

To join, open Rust, hit F1, and enter client.connect 217.235.33.249:28015. Or click Launch Rust on this page to open the game through Steam and connect.

What each one means

Server tags

Published as mp10,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust does it.
mp10
Max players The slot count is 10.
ts8
Group limit It uses the default team limit: 8.
v2633
Protocol To join, your game has to be on protocol 2633.
cs163207
Build It's on build 163207.
ptrak
Networking The network layer is RakNet, Rust's default.
$r?
Region code No region is set.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded You'll see it in Modded, since plugins or settings modify the game.

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.