testing
Online NA 157.85.86.76:21595 checked 7m ago
Server instruments
last reading Wed 08:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 231 · below 20 is lag, below 10 is badEntities
48 h range 3,001–7,087 · memory 2,355 MBUptime
1 days 21 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 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 #378 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 6h. Its weekly schedule tag · low confidence
Coming wipes
- WPT 1Sat 31 Oct, 16:01 UTC3d 6h
- WPT 2Thu 5 Nov, 19:00 UTC8d 9hFW
- WPT 3Sat 7 Nov, 16:01 UTC10d 6h
- WPT 4Sat 14 Nov, 16:01 UTC17d 6h
- WPT 5Sat 21 Nov, 16:01 UTC24d 6h
- WPT 6Sat 28 Nov, 16:01 UTC31d 6h
- WPT 7Thu 3 Dec, 19:00 UTC36d 9hFW
- WPT 8Sat 5 Dec, 16:01 UTC38d 6h
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- 2/100
- 108/150
- 0/100
- 0/100
- 2/100
- 19/200
Quick answers
from the figures on this pageReset cycle
What happens on testing when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.
When does testing wipe?
Its tag guides the prediction: too few of testing's wipes are on record to confirm its schedule. Saturday 31 October at 16:01 UTC is when its next wipe is due. The world in play was created 3 days 17 hours ago. A weekly wipe schedule is published in its tags.
Tag meanings
Which tags does testing carry, and what do they mean?
These are the tags testing publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp20 (Max players): Slots: 20; ts2 (Group limit): Team cap: 2; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^w (Weekly): It wipes each week; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon; NA (North America): Its browser listing: North America. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show testing?
On Rust Metrics, testing sits in these lists: Duo Rust servers, Modded Rust servers, checked live and North America: server readout. Reading: server list filters. It comes up under 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 count
What position does testing hold among Rust servers?
Ranked by seven-day player hours, testing sits at #15,396 and #1,541 in North America, inside the top 69%. Among servers in duo, it stands at #378.
What is the population on testing?
0 of 20 slots are filled on testing right now. Seven-day reading: 0 players on average.
Server details
Which location does testing run from?
Its NA tag places testing in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 157.85.86.76:21595.
What Rust version is testing on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by testing. Check: protocol. To join, your game must match; Steam handles the update.
How does testing perform?
Reading: 239 server fps on average across the last 48 hours. It never dropped below 231. Peak entity count: 7,087. Buildings, deployables and all else included. Memory peak: 2,814 MB. Expect lag when fps falls and entities climb.
How reliable is testing, and is it online now?
testing reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 45 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 16 October 2026.
Settings and map
What settings and rules apply on testing?
Reading the name gives no gather rate for testing. Check: group limit. 2 players, under the name duo. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.
What map is testing on?
Size 1,000 and seed 50000: the game generates the procedural map on testing from them. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.
Connection
How do you connect to testing?
Press F1 in Rust and enter client.connect 157.85.86.76:21595. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://discord.com/invite/BGKzykfwEC.