[TEST] WipeDay Test
Online 104.128.58.197:28015 checked 11m ago
Measurements
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not 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
| 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.
Quick answers
Population
How does [TEST] WipeDay Test rank against other Rust servers?
The last seven days of player hours place [TEST] WipeDay Test at #15,351, within the top 69% of all ranked servers.
How busy is [TEST] WipeDay Test?
The count reads 0 players on [TEST] WipeDay Test, which has 50 slots. We counted 0 players on average across the past week.
Lists and tags
What do the server tags on [TEST] WipeDay Test mean?
The game's server browser reads the tags [TEST] WipeDay Test publishes: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): To join, your game must match protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings change the game; it is listed under Modded; ^y (Carbon): A plugin framework, Carbon, is in use. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.
Which Rust Population lists and filters include [TEST] WipeDay Test?
On Rust Population, [TEST] WipeDay Test is filed under these lists: Modded Rust servers, counted. Look for 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.
Wipe notes
What does wipe day look like on [TEST] WipeDay Test?
Averaged over recent wipes, 0 players were counted at the busiest point. Peak came 0 hours into the latest wipe.
What is the wipe schedule on [TEST] WipeDay Test?
The record holds too few of [TEST] WipeDay Test's wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. Counted from 13 days 11 hours ago, that is how long the current world has stood.
Map and rules
Which map does [TEST] WipeDay Test run?
[TEST] WipeDay Test uses a map the game generates, procedural, at size 1,500 with seed 249036398. You can look at it on RustMaps from this page: size and seed determine the map.
What are the rules and settings on [TEST] WipeDay Test?
The name tells you nothing about gather rates: [TEST] WipeDay Test states none. Eight players per group is the default, and it applies here. You get survival here, raid, build and gather: the standard game. You can raid and fight other players here. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Carbon. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does [TEST] WipeDay Test run?
On Linux, [TEST] WipeDay Test runs Rust network protocol 2634 and build 167781. Your game needs the same protocol to join; Steam takes care of updating it.
Does [TEST] WipeDay Test run smoothly?
In the last 48 hours, it averaged 239 server fps, with a low of 238. The entity count reached 7,905: buildings, deployables and all other objects. The highest memory usage was 1,475 MB. Players feel lag when fps is low and the entity count climbs.
Is [TEST] WipeDay Test online, and how reliable is it?
You will find [TEST] WipeDay Test online now. The uptime it reports suggests a restart roughly 4 days 20 hours ago. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. The first sighting by Rust Population was on 14 October 2026.
Where is [TEST] WipeDay Test located?
Nothing published by [TEST] WipeDay Test states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. 104.128.58.197:28015 is where it lives.
How to join
How do I join [TEST] WipeDay Test?
To connect directly, open Rust's console with F1 and type client.connect 104.128.58.197:28015; or press Launch Rust on this page and Steam opens Rust and joins for you. You can find its website at https://wipeday.thunderdome.gg.