testing
NA 157.85.86.76:21595 checked 14m ago
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 16 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 37% of all ranked servers, top 64% in NA, and #312 of the duo servers (top 72%). Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Saturday 24 October, 15:10 UTC, in 6d 13h. Its weekly schedule tag · low confidence
Coming wipes
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 17 Oct, 15:10 UTC10h ago | – | – | running | 1 |
| Fri 16 Oct, 10:42 UTC1d ago | – | – | – | 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
Quick answers
Map and rules
What is the setup on testing when it comes to rules and settings?
No gather rate appears in the name testing. A group can hold 2 players at most (duo). survival is the game mode, gather, build and raid: the standard game. Other players can be fought and raided. This one sits under Modded in the browser: the game is changed by plugins or settings. It runs plugins: Carbon. Anti-cheat is on: VAC, from Valve.
What is the map on testing?
A procedural map, size 1,000 with seed 50000, generated by the game, is what testing runs. Same size and seed, same map: RustMaps shows it from this page. Under map name you will find: Custom Map.
Population
How many players are on testing?
testing has 0 of its 20 slots filled right now. Averaging 0 players over seven days, it peaked at 1. The highest average over the last 48 hours came at 06:00 UTC, with 1 players.
What position does testing hold in the server rankings?
In North America, testing is #1,186, and globally it is #8,173 for player hours over the last seven days, within the top 37% of all ranked servers. It is #312 when compared with other duo servers.
Server tags
How should you read the tags on testing?
For the game's server browser, testing publishes these tags: gmvanilla (Game mode): This is vanilla survival; mp20 (Max players): The server has 20 slots; ts2 (Group limit): Teams are capped at 2; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs167781 (Build): It runs build 167781; ptrak (Networking): Standard RakNet networking is in use here; $r? (Region code): There's no region code here; ^w (Weekly): Wipes: weekly; ^z (Modded): The Modded listing means plugins or settings have changed the game; ^y (Carbon): Carbon plugin framework is running; NA (North America): North America is the category it falls under in the server browser. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.
Where does testing appear in Rust Zerg Life lists?
The Rust Zerg Life lists that include testing are Duo Rust servers, listed straight, Modded Rust servers for clans and zergs and North American Rust servers. Under these filters it shows 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 24 hours.
Server info
What is the uptime and reliability of testing?
testing is up and running as you read this. The uptime figure it gives suggests it restarted around 8 hours ago. It was online 100% of the time over the last 1 full day: 24 hours out of 24. The first time Rust Zerg Life saw it was on 16 October 2026.
Is testing smooth to play on?
Over the past 48 hours, server fps averaged 239 and never dropped below 231. It reached a maximum of 6,318 entities, covering buildings, deployables and the rest of the world. The maximum memory it used was 3,351 MB. Lag, as players feel it, is caused by low fps and an increasing number of entities.
What version is testing using?
On Linux, testing runs Rust network protocol 2634 and build 167781. The protocol must match for you to join, and Steam will update your game to that protocol.
What location does testing use?
In North America, testing lists itself with its NA tag. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. Connect to it at 157.85.86.76:21595.
Wipe cycle
How often does testing wipe, and on what days?
Its tag guides the prediction, as testing's wipe record is too sparse to confirm the schedule. On Saturday 24 October at 15:10 UTC its next wipe is expected. The world in play right now was made 9 hours ago. A wipe every week is what its tags state.
Connect
How can I connect to testing?
Join by entering client.connect 157.85.86.76:21595 in the console (press F1 first). Or use Launch Rust on this page, which opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/BGKzykfwEC.
Server tags
Published as mp20,ptrak,$r?,v2634,^z,^y,^w,NA,gmvanilla,cs167781,ts2
Game
gmvanilla
mp20
ts2
v2634
cs167781
ptrak
$r?
Wipe schedule
^w
Mods and access
^z
^y
Region
NA
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.