testing
Online NA 157.85.86.76:21595 checked 11m 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, measured since 16 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, top 82% in NA, and #381 of the duo servers (top 90%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Saturday 31 October, 16:01 UTC, in 3d 15h. Its weekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 3d 15h | Sat 31 Oct, 16:01 UTC | its own |
| 8d 18h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 10d 15h | Sat 7 Nov, 16:01 UTC | its own |
| 17d 15h | Sat 14 Nov, 16:01 UTC | its own |
| 24d 15h | Sat 21 Nov, 16:01 UTC | its own |
| 31d 15h | Sat 28 Nov, 16:01 UTC | its own |
| 36d 18h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 38d 15h | Sat 5 Dec, 16:01 UTC | its own |
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 |
|---|---|---|---|---|
| Sat 24 Oct, 16:01 UTC3d ago | 0 | – | running | 0 |
| Sat 17 Oct, 15:10 UTC10d ago | 1 | halved by day 1 | 7 days | 1 |
| Fri 16 Oct, 10:42 UTC11d ago | 1 | – | 1.2 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| Server | Profile | Players now |
|---|---|---|
| RustForNoobs.com | Solo/Duo | Weekly | US | NA · duo · weekly · 100 on average | 41 / 100 |
| RustForNoobs.com | Mondays | Solo/Duo | US | NA · duo · weekly · 60 on average | 254 / 250 |
| US RustLife.net | Solo/Duo | Fridays | Noob Friendly | NA · duo · weekly · 3 on average | 1 / 100 |
| WARBANDITS.GG |Solo/Duo|Weekly| JUST WIPED | NA · duo · weekly · 3 on average | 3 / 100 |
| US RustLife.net | Solo/Duo | Mondays | Noob Friendly | NA · duo · weekly · 2 on average | 4 / 100 |
| WARBANDITS.GG 2X |Solo/Duo|X2 JUST FULLWIPED | NA · duo · 2x · weekly · 147 on average | 46 / 200 |
Quick answers
from the figures on this pageWipe data
The wipe schedule for testing: what is it?
The tag sets the prediction: too few of testing's wipes are on record to confirm its schedule. Saturday 31 October at 16:01 UTC is the date the next wipe falls on. The world now in play was created 3 days 8 hours ago. The tags list a wipe schedule of one week.
On testing, what happens on wipe day?
Recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe the crowd peaked. Above half that peak until the next wipe held in 0% of recent wipes. In the other cases the crowd dropped below half by day 1.
Server details
In which region does testing sit?
The NA tag on testing lists it in North America. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 157.85.86.76:21595 is its address.
What Rust build does testing run?
On Linux, testing runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.
How reliable is testing, and is it online now?
testing reports online at the current check. Its reported uptime indicates a restart roughly 36 hours ago. Of 168 hours in the last 7 full days, 168 were up: 100%. The first sighting of it by Rust Server Analytics was on 16 October 2026.
What performance does testing show?
Over 48 hours the average held at 238 server fps, and the minimum was 223. Buildings, deployables and all other world objects brought the entity total to 7,087. Memory use reached 2,983 MB at peak. Players experience lag as low fps combined with a rising entity count.
Lists and tags
What do testing's tags stand for?
gmvanilla (Game mode): The vanilla survival format; mp20 (Max players): Capacity of 20 slots; ts2 (Group limit): The cap is 2 players per team; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^w (Weekly): Wipes run on a weekly cycle; ^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. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
Where does testing appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include testing: Duo Rust servers, Modded Rust servers: live data and North America Rust servers. It appears on the server list under the following filters: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly; Last wipe: In the last week.
Player numbers
Where does testing sit among Rust servers?
Ranked on seven-day player hours, testing is #15,414 overall and #1,546 in North America, within the top 69% of ranked servers. Within the duo segment, its position is #381.
How many players does testing carry?
testing holds 0 players of its 20 slots as of the latest update. The seven-day mean for this server is 0 players.
Settings
What settings and rules does testing use?
No gather rate is given in the name of testing. Groups: duo, capped at 2 players. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Carbon. The server runs with VAC, Valve's anti-cheat, enabled.
What is the map for testing?
The game generates a procedural map of size 1,000 with seed 50000 for testing. The map is reproducible from its size and seed and can be seen on RustMaps from here. The name of the map is Custom Map.
How to join
How can a player join testing?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 157.85.86.76:21595. https://discord.com/invite/BGKzykfwEC is its website.