Testing
Online 90.146.82.82:28035 checked 10m 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 53% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
- 944/ 100
- 171/ 400
- 130/ 245
- 125/ 100
- 384/ 1000
- 25/ 700
Quick answers
Tags and filters
Where does Testing appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Testing are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on Testing?
gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): It holds 10 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): It's on build 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): Carbon is the plugin framework it uses — that is the tag list Testing puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is Testing in?
Testing does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 90.146.82.82:28035.
What's the uptime like for Testing?
Right now Testing is online. Over the past full 7 days it stayed up for 165 of 168 hours, or 98%. 6 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for Testing?
On Linux, Testing runs Rust network protocol 2634 and build 167781. The protocol must match to join; Steam will update your game.
Wipe info
How often does Testing wipe?
The wipes recorded for Testing are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 11 days 1 hours ago.
Settings and map
What settings are in place on Testing?
No gather rate appears in the name of Testing. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Carbon. VAC, Valve's anti-cheat, is enabled.
Which map is active on Testing?
A procedural map, generated by the game, is in play on Testing.
Player count
What's the population like on Testing?
Right now 0 players are on Testing, which has 10 slots. The seven-day average is 0 players, with a peak of 1. Over the last 48 hours, 22:00 UTC drew the most players, 1 on average.
What's Testing's rank among Rust servers?
For player hours in the last seven days, Testing ranks #11,636, within the top 53% of ranked servers.
Getting in
What's the way to join Testing?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 90.146.82.82:28035.