testing
Online NA 157.85.86.76:21595 checked 10m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 69% of all ranked servers, top 82% in NA, and #369 of the duo servers (top 88%). Ranked on player hours over the last seven days.
Bx1Wipe schedule
from its schedule tagNext wipe Saturday 31 October, 16:01 UTC, in 2d 16h. Its weekly schedule tag · low confidence
Coming 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 16:01 UTC4d ago | 0° | – | running | 0 |
| Sat 17 Oct, 15:10 UTC11d ago | 1° | halved by day 1 | 7 days | 1 |
| Fri 16 Oct, 10:42 UTC12d 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on testing?
Its recent wipes drew an average peak of 1 players. 0 hours into the latest wipe, player numbers topped out. Above half the peak until the next wipe: that held in 0% of its recent wipes. By day 1 it was below half in the wipes that did not hold.
What is the wipe schedule on testing?
Too few wipes are recorded on testing to confirm its schedule; the tag is what the prediction follows. Due on Saturday 31 October at 16:01 UTC: the next wipe. The world it runs now dates from 4 days 7 hours ago. A weekly wipe is declared in its tags.
Population
How busy is testing?
testing currently has 0 of its 20 slots filled. A seven-day average of 0 players.
How does testing rank against other Rust servers?
Top 69% of ranked servers and #1,521 in North America: that is testing at #15,349 for player hours over seven days. The duo group puts it at #369.
Map and rules
Which map does testing run?
The map on testing is procedural, size 1,000 with seed 50000, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map. The name of the map is: Custom Map.
What are the rules and settings on testing?
A gather rate is not given in the name testing. 2 players is the maximum group size (duo). The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. The server browser lists it as Modded: plugins or settings change the game. Carbon plugins are in use. The server has VAC, Valve's anti-cheat, turned on.
Server details
Which version of Rust does testing run?
Rust network protocol 2635 and build 168909 on Linux is what testing runs. Your game must run the same protocol to join, and Steam takes care of updating it.
Is testing online, and how reliable is it?
Right now testing shows as online. The uptime it reports puts the last restart at about 2 days 11 hours ago. 144 of 168 hours up over the last 7 full days, which is 86%. Rust Heatmap has had it on record since 16 October 2026.
Where is testing located?
With its NA tag, testing lists itself in North America. Rust Heatmap shows the location a server states. It does not look up the machine's location. You can reach it at 157.85.86.76:21595.
Does testing run smoothly?
It averaged 239 server fps over the last 48 hours, with a low of 231. Buildings, deployables and the rest of the world came to as much as 7,034 entities. At its peak it held 2,919 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.
Tags
Which Rust Heatmap lists and filters include testing?
These Rust Heatmap lists include testing: Rust servers with a group limit of 2, Modded Rust servers, by live population and North America server heatmap. You will find it under these filters on the server list: 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.
What do the server tags on testing mean?
gmvanilla (Game mode): The vanilla survival game; mp20 (Max players): The slot count is 20; ts2 (Group limit): A team holds no more than 2; v2635 (Protocol): Your game must match protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set; ^w (Weekly): A wipe every week; ^z (Modded): Listed as Modded, since settings or plugins change the game; ^y (Carbon): Plugins run through Carbon; NA (North America): North America is where the server browser puts it are the tags testing publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join testing?
Enter client.connect 157.85.86.76:21595 in the console, opened with F1 in Rust. Or use Launch Rust here, which opens the game through Steam and connects you. The server's site sits at https://discord.com/invite/BGKzykfwEC.