Station XX-15341 · recording
[TEST] WipeDay Test
Online 104.128.58.197:28015 checked 12m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,341
- top 69%
- Last wipe
- 13d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
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.
- usual gap
- 1.1 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 18:01 UTC13d ago | M0.0■steady | 0 | – | running | 0 | |
| Wed 14 Oct, 14:47 UTC14d ago | M0.0■steady | 0 | – | 1.1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on [TEST] WipeDay Test?
[TEST] WipeDay Test runs a procedural map of size 1,500 with seed 249036398, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on [TEST] WipeDay Test?
The name of [TEST] WipeDay Test gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on [TEST] WipeDay Test?
At this moment, [TEST] WipeDay Test records 0 players across 50 slots. The seven-day average for this server is 0 players.
How does [TEST] WipeDay Test rank against other Rust servers?
The last seven days of player hours place [TEST] WipeDay Test at #15,341, in the top 69% of all ranked servers.
Operator and location
How reliably does [TEST] WipeDay Test stay online?
[TEST] WipeDay Test is up at the moment. The uptime it reports puts its last restart about 4 days 22 hours ago. It was up 99% of the time across the last 7 full days: 167 of 168 hours. 14 October 2026 is when Rust Server Trends first recorded it.
Does [TEST] WipeDay Test hold a steady tick rate?
The 48-hour average is 239 server fps; 238 is the lowest observed. The world held up to 7,905 entities at its peak, buildings and deployables included. Its highest memory use was 1,475 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is [TEST] WipeDay Test hosted?
No region is published by [TEST] WipeDay Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 104.128.58.197:28015.
What build of Rust does [TEST] WipeDay Test use?
On Linux, [TEST] WipeDay Test runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on [TEST] WipeDay Test?
On average, the busiest point of its recent wipes drew 0 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does [TEST] WipeDay Test run its wipes?
On record so far are too few of [TEST] WipeDay Test's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 13 days 12 hours is how long the current world has been running.
Lists and tags
What do the server tags on [TEST] WipeDay Test mean?
These are the tags [TEST] WipeDay Test publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does [TEST] WipeDay Test appear?
The Rust Server Trends lists that take in [TEST] WipeDay Test are: Modded Rust servers, tracked live. You will find it under these filters 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.
Connecting
How do you connect to [TEST] WipeDay Test?
You can connect by pressing F1 in Rust and typing client.connect 104.128.58.197:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://wipeday.thunderdome.gg.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.