testing
Offline NA 153.66.141.225:28015 checked 16d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers, top 84% in NA, and #376 of the duo servers (top 87%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Saturday 31 October, 15:49 UTC, in 1d 13h. Its weekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 1d 13h | Sat 31 Oct, 15:49 UTC | its own |
| 6d 16h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 8d 13h | Sat 7 Nov, 15:49 UTC | its own |
| 15d 13h | Sat 14 Nov, 15:49 UTC | its own |
| 22d 13h | Sat 21 Nov, 15:49 UTC | its own |
| 29d 13h | Sat 28 Nov, 15:49 UTC | its own |
| 34d 16h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 36d 13h | Sat 5 Dec, 15:49 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 10 Oct, 15:49 UTC19d ago | 1 | – | running | 1 |
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| Server | Profile | Players now |
|---|---|---|
| RustForNoobs.com | Solo/Duo | Weekly | US 10/29 10.29 | NA · duo · weekly · 97 on average | 320 / 350 |
| RustForNoobs.com | Mondays | Solo/Duo | US | NA · duo · weekly · 72 on average | 72 / 100 |
| US RustLife.net | Solo/Duo | Fridays | Noob Friendly | NA · duo · weekly · 3 on average | 4 / 100 |
| WARBANDITS.GG |Solo/Duo|Weekly| JUST WIPED | NA · duo · weekly · 2 on average | 1 / 100 |
| US RustLife.net | Solo/Duo | Mondays | Noob Friendly | NA · duo · weekly · 2 on average | 3 / 100 |
| WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED | NA · duo · 2x · weekly · 149 on average | 179 / 225 |
Quick answers
from the figures on this pageWipe data
The wipe schedule for testing: what is it?
Its tag guides the prediction, since testing has too few wipes on record to confirm the schedule. Saturday 31 October at 15:49 UTC is when its next wipe is due. 19 days 10 hours ago the current world was made. Its tags carry a weekly wipe schedule.
Wipe day on testing: what should you expect?
Across recent wipes the busiest point averaged 1 players. The highest player count on the latest wipe arrived 1 hours in.
Server details
What is the hosting location of testing?
The NA tag on testing lists it in North America. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. You will find it at 153.66.141.225:28015.
What Rust build does testing run?
The platform is Windows, with Rust network protocol 2634 and build 166652 running on testing. Joining requires the same protocol on your game; Steam handles the update.
What uptime does testing show, and is it up?
Offline at this refresh: testing, last seen 16 days ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. 9 October 2026 is when Rust Server Analytics first recorded it.
Lists and tags
What do testing's tags stand for?
gmvanilla (Game mode): Vanilla ruleset survival; mp20 (Max players): Capacity of 20 slots; ts2 (Group limit): Teams hold no more than 2; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs166652 (Build): Game build: 166652; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): The region code is blank; ^w (Weekly): The server wipes each week; ^z (Modded): Plugins or settings change the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon; NA (North America): The server browser files it under North America are the tags testing publishes, and the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On Rust Server Analytics, which lists and filters feature testing?
These Rust Server Analytics lists include testing: Duo Rust servers, Modded Rust servers: live data and North America Rust servers. On the server list, the filters that return it are: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly.
Population
Against other Rust servers, how does testing compare?
testing holds #15,215 on seven-day player hours and #1,545 in North America, inside the top 71% of the ranked field. In the duo peer group, the rank is #376.
How many players does testing carry?
The last sighting of testing was 16 days ago; it is offline at this refresh.
Map and rules
How is testing configured, and what rules apply?
Gather rate is not mentioned in the name of testing. A maximum of 2 players per group is set (duo). survival is the game mode, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Carbon are in use. VAC, Valve's anti-cheat, is enabled.
Connection
How do you connect to testing?
In the Rust console (F1), enter client.connect 153.66.141.225:28015. Launch Rust on this page also works, opening Rust through Steam and connecting you.