Rust Data LabData lab · live
Live readings Servers11,781 Players76,222 Populated3,531 Fresh wipes · 3h245 Sampled every 5 min

Element card · group Community · atomic number 14,669, its rank

TEST

Offline 195.3.134.234:28015 checked 23d ago

Join the experiment
Atomic mass · players now 1/ 5 20% full Room to join
7-day average0peak –
Rank · atomic number#14,669top 66%
Last wipe23d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 66% 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 peak1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 6 Oct, 20:40 UTC23d ago 1 – running 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… 168
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 503 on average 168/ 250
  2. 2 Ru Rustoria.co - … 194
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 194/ 250
  3. 3 Ru Rusty Moose |E… 619
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 282 on average 619/ 675
  4. 4 Ru Rustafied.com … 35
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 277 on average 35/ 100
  5. 5 Ru Rustoria.co - … 709
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average 709/ 775
  6. 6 Ru Rustoria.co - … 561
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 245 on average 561/ 625

Quick answers

from the figures on this page

Settings and map

What map is in play on TEST?

A procedural map runs on TEST, generated by the game.

What settings and rules apply on TEST?

No gather rate appears in the name of TEST. With no change from the default, groups can hold up to 8 players. Play runs as survival, raiding, building and gathering: the standard game. You can fight other players and raid them. The server browser lists it under Community. VAC is on, Valve's anti-cheat.

About the server

In what location does TEST sit?

No region is published by TEST. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 195.3.134.234:28015 is the address it uses.

On what Rust version does TEST operate?

On Windows, TEST is running Rust network protocol 2634 and build 166652. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is TEST for staying online?

TEST is not online at the moment; the last sighting was 23 days 1 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 6 October 2026.

Wipe schedule

How often does a wipe happen on TEST, and at what time?

TEST's wipe history on record is too thin yet to tell 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 23 days 2 hours ago.

On TEST, what happens when wipe day arrives?

Averaged across its recent wipes, the busiest point drew 1 players. 0 hours after the latest wipe, the crowd peaked.

Lists and tags

What should you understand from the tags TEST carries?

These are the tags TEST makes public for the server browser to read: 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; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): A region code has not been set here. 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 TEST come up?

These themed Rust Data Lab lists carry TEST: 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 TEST compare with other servers in the rankings?

Player hours over the last week put TEST at #14,669, inside the top 66% of ranked servers.

What does the current player count on TEST tell you?

No live signal from TEST right now, which was last seen 23 days 1 hours ago.

Connection

How can you connect to TEST?

Open the console with F1 in Rust and type client.connect 195.3.134.234:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

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.
v2634
Protocol To join, your game must match protocol 2634.
cs166652
Build Build number: 166652.
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.