Rust Data LabData lab · live
Live readings Servers11,894 Players101,584 Populated3,939 Fresh wipes · 3h404 Sampled every 5 min

Element card · group Modded · atomic number 13,625, its rank

Private - Raid Type Test

Online 157.85.94.33:20552 checked 9m ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 5 0% full Room to join
7-day average0peak 1
Rank · atomic number#13,625top 61%
Last wipe14d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.250.50.75118:0003:0012:0022:0007:0016:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
010020030040018:0003:0012:0022:0007:0016:00

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, measured since 15 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k15 Oct18 Oct21 Oct23 Oct26 Oct29 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

too few wipes seen yet

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

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 15 Oct, 14:55 UTC14d ago 2 – running 1

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
  1. 1 Sh ShockRust | Bl… 160
    ShockRust | Blue | NoLimit no group limit · 151 on average 160/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 120
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 120/ 100
  3. 3 Re RETRO RUST #1 … 191
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 191/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 97
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average 97/ 700
  5. 5 Ru 404 RUST 2Х|ДЛ… 230
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 88 on average 230/ 700
  6. 6 Ru RustSpain.com … 345
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 84 on average 345/ 350

Quick answers

from the figures on this page

Settings and map

What map is in play on Private - Raid Type Test?

A procedural map of size 3,000 with seed 1337 runs on Private - Raid Type Test, generated by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

How is Private - Raid Type Test configured, and what rules apply?

The name of Private - Raid Type Test carries no gather rate. With no change from the default, groups can hold up to 8 players. survival is the game mode, gather, build and raid, as in the standard game. You can fight other players and raid them. The server browser lists it under Modded, where plugins or settings change the game. The plugin count is Oxide. VAC is on, Valve's anti-cheat.

About the server

What region hosts Private - Raid Type Test?

No region is published by Private - Raid Type Test. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. You will find it at 157.85.94.33:20552.

What Rust version does Private - Raid Type Test currently run?

Rust network protocol 2635 and build 167781 on Linux is what Private - Raid Type Test uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How reliably does Private - Raid Type Test stay online?

Right now, Private - Raid Type Test is reachable. The uptime it reports suggests it restarted roughly 3 hours ago. For the last 7 full days, 167 of 168 hours were online, giving 99% uptime. On 15 October 2026, Rust Data Lab saw it for the first time.

How well does Private - Raid Type Test perform?

Server fps averaged 194 over the last 48 hours, with 142 as the lowest. Buildings, deployables and everything else in the world added up to as many as 47,347 entities. Up to 4,954 MB of memory was used. Players feel lag when fps is low and the entity count climbs.

Wipes and resets

What is the wiping pattern on Private - Raid Type Test?

The record holds too few of Private - Raid Type Test's wipes to show its rhythm. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. 14 days 2 hours ago the current world was made.

On Private - Raid Type Test, what happens when wipe day arrives?

At their busiest, recent wipes averaged 2 players. 2 hours after the latest wipe, the crowd peaked.

Tags, lists

What should you understand from the tags Private - Raid Type Test carries?

gmrust (Game mode): Survival in the standard Rust style; mp5 (Max players): It has 5 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs protocol 2635, so your game needs the same version; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it lists under Modded: that is the tag list Private - Raid Type Test publishes, and the game's server browser reads it. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Where among the Rust Data Lab lists and filters does Private - Raid Type Test come up?

These themed Rust Data Lab lists carry Private - Raid Type Test: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player numbers

How does Private - Raid Type Test compare with other servers in the rankings?

The seven-day player-hours table has Private - Raid Type Test at #13,625, in the top 61% of ranked servers.

How full is Private - Raid Type Test right now?

At the moment Private - Raid Type Test has 0 of its 5 slots filled. A seven-day sample gives 0 players on average and 1 at the top. Peak time in the past 48 hours: 18:00 UTC, when the average was 1 players.

Connection

What steps get you onto Private - Raid Type Test?

In Rust, press F1 and enter client.connect 157.85.94.33:20552. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp5,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp5
Max players It has 5 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol The server runs protocol 2635, so your game needs the same version.
cs167781
Build Build number: 167781.
ptrak
Networking The network layer is RakNet, standard in the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it lists under Modded.

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.