TST15349=
[TEST] WipeDay Test
Online 104.128.58.197:28015 checked 12m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
-
01MODPlayers 38/500
-
02MODPlayers 135/100
-
03MODPlayers 40/225
-
04MODPlayers 34/700
-
05MODPlayers 7/200
-
06MODPlayers 5/1000
Quick answers
From the figures on this page.
Filters
Where does [TEST] WipeDay Test appear in Rust Tracker lists and filters?
These Rust Tracker lists carry [TEST] WipeDay Test: Modded servers, tracked live. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on [TEST] WipeDay Test?
The game's server browser reads these tags from [TEST] WipeDay Test: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): Capacity: 50 slots; ts8 (Group limit): Default team size: 8; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): This server runs game build 167781; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set; ^z (Modded): Under Modded: the game is changed by plugins or settings; ^y (Carbon): Carbon is installed — a plugin framework. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Schedule
What should you expect on [TEST] WipeDay Test when wipe day lands?
The average peak across recent wipes: 0 players. The peak on the latest wipe came 0 hours after it.
When does [TEST] WipeDay Test wipe?
The record holds too few of [TEST] WipeDay Test's wipes to show its rhythm. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. 13 days 7 hours since this world was made.
Location and Status
What is the uptime on [TEST] WipeDay Test, and is it online?
[TEST] WipeDay Test is up and online at this moment. By its own uptime figure, the last restart was roughly 4 days 15 hours ago. 99% uptime over the last 7 full days, with 167 of 168 hours up. First contact for Rust Tracker: 14 October 2026.
What Rust version is [TEST] WipeDay Test on?
Confirmed for [TEST] WipeDay Test: Rust network protocol 2634 and build 167781, Linux. To join, your game must be on the same protocol; Steam handles the update.
Is [TEST] WipeDay Test holding performance?
Average server fps over the last 48 hours: 239, with a low of 238. Maximum entities carried: 7,826, from buildings and deployables to everything else. Peak memory use: 1,475 MB. Players feel lag when fps drops and the entity count climbs.
Which location is [TEST] WipeDay Test in?
Nothing on region from [TEST] WipeDay Test; none is published. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 104.128.58.197:28015.
Player Count
Is [TEST] WipeDay Test busy?
Slots 50; players on board 0: that is [TEST] WipeDay Test now. Across the past seven days, 0 players on average.
What rank does [TEST] WipeDay Test carry among Rust servers?
Seven-day player hours put [TEST] WipeDay Test at #15,349, within the top 69% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on [TEST] WipeDay Test?
No gather rate appears in [TEST] WipeDay Test's name. 8 players per group is the game's default, and the cap holds. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Carbon. On: VAC, Valve's anti-cheat.
Which map is loaded on [TEST] WipeDay Test?
Generated by the game from seed 249036398, the procedural map on [TEST] WipeDay Test measures 1,500. Size and seed match, so the map is the same: view it on RustMaps from this page.
Connect
What is the way to join [TEST] WipeDay Test?
To connect: start Rust, press F1, enter client.connect 104.128.58.197:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join. For the website, go to https://wipeday.thunderdome.gg.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
mp50
ts8
v2634
cs167781
ptrak
$r?
Mods and access
^z
^y
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.