[TEST] WipeDay Test
Online 104.128.58.197:28015 checked 12m ago
Server instruments
last reading Thu 05:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 238 · below 20 is lag, below 10 is badEntities
48 h range 5,620–7,905 · memory 1,312 MBUptime
4 days 22 hours since its last restart, at the last readingPlayers
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- 65/500
- 122/100
- 99/225
- 31/700
- 3/200
- 8/1000
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on [TEST] WipeDay Test?
The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does [TEST] WipeDay Test follow?
Its rhythm cannot be told from the wipes of [TEST] WipeDay Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 13 days 12 hours ago the current world was made.
Tags
Which tags does [TEST] WipeDay Test carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Plugin framework in use: Carbon from [TEST] WipeDay Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show [TEST] WipeDay Test?
On Rust Metrics, [TEST] WipeDay Test sits in these lists: Modded Rust servers, checked live. 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 count
What position does [TEST] WipeDay Test hold among Rust servers?
Player hours over seven days put [TEST] WipeDay Test at #15,341, in the top 69% of all ranked servers.
What player count does [TEST] WipeDay Test carry?
Current headcount on [TEST] WipeDay Test: 0 players, 50 slots available. Check: player average. 0 over the last seven days.
Server
Where does [TEST] WipeDay Test sit?
No region tag on [TEST] WipeDay Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 104.128.58.197:28015.
What Rust version is [TEST] WipeDay Test on?
Reading: [TEST] WipeDay Test, Rust network protocol 2634 and build 167781, Linux. Check: protocol. To join, your game must match; Steam handles the update.
How does [TEST] WipeDay Test perform?
Over the last 48 hours the average was 239 server fps; the floor was 238. Reading: 7,905 entities at the highest. That covers buildings, deployables and everything else. Reading: 1,475 MB of memory at the highest. Expect lag when fps falls and entities climb.
How reliable is [TEST] WipeDay Test, and is it online now?
Check: connection. [TEST] WipeDay Test is online at this moment. Reading: uptime. About 4 days 22 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 14 October 2026.
Map and rules
What settings and rules apply on [TEST] WipeDay Test?
Reading the name gives no gather rate for [TEST] WipeDay Test. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.
Which map is live on [TEST] WipeDay Test?
From seed 249036398, the game generates the procedural map on [TEST] WipeDay Test. Its size is 1,500. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
How can you get onto [TEST] WipeDay Test?
Check: join. Open Rust, press F1, then enter client.connect 104.128.58.197:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://wipeday.thunderdome.gg is where its website sits.