Rust Data LabData lab · live
Live readings Servers11,633 Players42,563 Populated3,050 Fresh wipes · 3h98 Sampled every 5 min

Element card · group Community · atomic number 15,413, its rank

typical TEST

Offline 9.244.16.170:28015 checked 38d ago

Join the experiment
Atomic mass · players now 0/ 100 0% full Room to join
7-day average0peak –
Rank · atomic number#15,413no region published
Last wipe39d 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
No hourly history yet.

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
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.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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.

usual gap1.9 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sat 19 SepThu 17 Sep
01234+0h+9h+19h+28h+38h+47h

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 19 Sep, 05:20 UTC39d ago 0 – running 0
Thu 17 Sep, 07:02 UTC41d ago 0 – 1.9 days 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 390
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 536 on average 390/ 350
  2. 2 Ru Rustoria.co - … 200
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 200/ 225
  3. 3 Ru Rustoria.co - … 22
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 318 on average 22/ 250
  4. 4 Ru Rusty Moose |E… 26
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 317 on average 26/ 250
  5. 5 Ru Rustoria.co - … 111
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 276 on average 111/ 225
  6. 6 Ru Rustafied.com … 38
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average 38/ 100

Quick answers

from the figures on this page

Server setup

What map is in play on typical TEST?

The map on typical TEST is procedural, made by the game.

What settings and rules apply on typical TEST?

Nothing in the name of typical TEST gives a 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. Raids and player fights are part of play here. The server browser lists it under Community. VAC is on, Valve's anti-cheat.

About the server

In what location does typical TEST sit?

There is no region on record for typical TEST. Rust Data Lab shows a server's stated location, not a verified position of the machine. 9.244.16.170:28015 is the address it uses.

On what Rust version does typical TEST operate?

On Linux, typical TEST is running Rust network protocol 2633 and build 164530. Joining requires the same protocol on your game; Steam takes care of updating it.

How dependable is typical TEST for staying online?

typical TEST is not online at the moment; the last sighting was 38 days 14 hours ago. It was online for 0 of 168 hours in the last 7 full days, which is 0% uptime. The first sighting by Rust Data Lab was on 16 September 2026.

Wipes and resets

What is the wiping pattern on typical TEST?

The record holds too few of typical TEST's wipes to show its rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 39 days ago.

On typical TEST, what happens when wipe day arrives?

Recent wipes on average reached 0 players at their busiest. 0 hours after the latest wipe, the crowd peaked.

Lists and tags

What should you understand from the tags typical TEST carries?

gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Player slots: 100; ts8 (Group limit): This uses the game's default: 8 per team; v2633 (Protocol): Protocol 2633 is required; join only if your game matches it; cs164530 (Build): The game build is 164530; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): A region code has not been set here: that is the tag list typical TEST publishes, and the game's server browser reads it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Where among the Rust Data Lab lists and filters does typical TEST come up?

The Rust Data Lab lists that include typical TEST are: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player numbers

How does typical TEST compare with other servers in the rankings?

The seven-day player-hours table has typical TEST at #15,413, in the top – of ranked servers.

How many players does typical TEST have at the moment?

typical TEST is offline at the moment; the last sighting was 38 days 14 hours ago.

Getting on

What steps get you onto typical TEST?

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

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players Player slots: 100.
ts8
Group limit This uses the game's default: 8 per team.
v2633
Protocol Protocol 2633 is required; join only if your game matches it.
cs164530
Build The game build is 164530.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code A region code has not been set here.

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.