Rust Data LabData lab · live
Live readings Servers11,692 Players37,024 Populated2,928 Fresh wipes · 3h87 Sampled every 5 min

Element card · group Modded · atomic number 15,353, its rank

[TEST] WipeDay Test

Online 104.128.58.197:28015 checked 12m ago

moddedcarbon
Join the experiment
Atomic mass · players now 0/ 50 0% full Room to join
7-day average0peak –
Rank · atomic number#15,353top 69%
Last wipe13d 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
0123403:0012:0021:0006:0015:0001: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
010020030040003:0012:0021:0006:0015:0001: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
15k10k15k20k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct

Top 69% 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.

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

The first 48 hours of its last wipes

Thu 15 OctWed 14 Oct
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
Thu 15 Oct, 18:01 UTC13d ago 0 – running 0
Wed 14 Oct, 14:47 UTC14d ago 0 – 1.1 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 Sh ShockRust | Bl… 27
    ShockRust | Blue | NoLimit no group limit · 155 on average 27/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 130
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 130/ 100
  3. 3 Re RETRO RUST #1 … 37
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average 37/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 13
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 13/ 700
  5. 5 Ru RustSpain.com … 4
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 4/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 1
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 1/ 1,000

Quick answers

from the figures on this page

Map and rules

What map is in play on [TEST] WipeDay Test?

A procedural map of size 1,500 with seed 249036398 runs on [TEST] WipeDay Test, generated by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps.

What settings and rules apply on [TEST] WipeDay Test?

No gather rate appears in the name of [TEST] WipeDay Test. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugin count is Carbon. The VAC anti-cheat from Valve is enabled.

Server facts

What region hosts [TEST] WipeDay Test?

Nothing about a region is published by [TEST] WipeDay 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 104.128.58.197:28015.

Which Rust version is [TEST] WipeDay Test on?

Rust network protocol 2634 and build 167781 on Linux is what [TEST] WipeDay Test uses. Your game needs to match the protocol to join, and Steam updates it automatically.

How reliably does [TEST] WipeDay Test stay online?

At the moment, [TEST] WipeDay Test is online. The uptime it reports suggests it restarted roughly 4 days 18 hours ago. For the last 7 full days, 167 of 168 hours were online, giving 99% uptime. It first appeared to Rust Data Lab on 14 October 2026.

Does [TEST] WipeDay Test hold a steady performance?

In the last 48 hours, it averaged 239 server fps, with a low of 238. The entity count reached 7,826, including buildings, deployables and all other world items. The highest memory usage was 1,475 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipe days

How often does a wipe happen on [TEST] WipeDay Test, and at what time?

Too few wipes are on record for [TEST] WipeDay Test to reveal a rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. Counting back, the current world began 13 days 8 hours ago.

On [TEST] WipeDay Test, what happens when wipe day arrives?

Recent wipes on average reached 0 players at their busiest. The latest wipe's peak fell 0 hours after it began.

Lists and tags

Which meanings sit behind the tags on [TEST] WipeDay Test?

gmrust (Game mode): Standard Rust survival is the game here; mp50 (Max players): Player slots: 50; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): The region field is left blank; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings; ^y (Carbon): The plugin framework here is Carbon: that is the tag list [TEST] WipeDay Test publishes, and the game's server browser reads it. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Which Rust Data Lab filters and lists does [TEST] WipeDay Test appear in?

These themed Rust Data Lab lists carry [TEST] WipeDay Test: Modded Rust servers, measured. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player numbers

What position does [TEST] WipeDay Test hold among Rust servers?

The seven-day player-hours table has [TEST] WipeDay Test at #15,353, in the top 69% of ranked servers.

How full is [TEST] WipeDay Test right now?

[TEST] WipeDay Test currently shows 0 players across 50 slots. Over seven days the mean player count is 0.

Getting on

What is the way to join [TEST] WipeDay Test?

Open the console with F1 in Rust and type client.connect 104.128.58.197:28015. The Launch Rust button on this page does the same job through Steam. For more, visit https://wipeday.thunderdome.gg.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode Standard Rust survival is the game here.
mp50
Max players Player slots: 50.
ts8
Group limit Teams cap at 8, which is the game default.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs167781
Build Build number: 167781.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code The region field is left blank.

Mods and access

^z
Modded You will find it under Modded: the game is altered by plugins or settings.
^y
Carbon The plugin framework here is Carbon.

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.