RS-12607Modded server
Testing
Online 90.146.82.82:28035 checked 13m 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
Top 56% 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
| 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.
Quick answers
From the figures on this page.
Population
How many players are usually on Testing?
On 10 slots, Testing has 0 players at this moment. A seven-day average of 0 players was reached, peaking at 1.
Where does Testing sit in the rankings?
On player hours across seven days, Testing is #12,607, inside the top 56% of all ranked servers.
Server tags and lists
Where does Testing appear among the Top Rust Servers lists and filters?
These Top Rust Servers lists include Testing: Top modded Rust servers. These are the filters that bring it up on the server list: 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?
The game's server browser reads the tags that Testing publishes: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): There are 10 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs167584 (Build): The game build is 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region code is left blank; ^z (Modded): This server is marked Modded, meaning plugins or settings alter the game; ^y (Carbon): This server uses Carbon for plugins. At the top of this page you also see its players now, its queue, and the time its world was made, taken from the tags.
Rules, settings, and map
What is the map on Testing?
Testing uses a procedural map, which the game generates.
What does Testing run for rules and settings?
You will not find a gather rate in the name Testing. The group limit is the game's default of 8 players. You play survival, gather, build and raid in the standard game. Player versus player combat and raiding are enabled. Plugins or settings change the game; it is listed as Modded. Carbon plugins are loaded. VAC, Valve's anti-cheat, is enabled.
About the server
What Rust version is Testing on?
On Linux, Testing operates Rust network protocol 2634 and build 167584. The protocol must match for you to join; Steam will update your game.
What is the location of Testing?
There is no region published by Testing. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. You reach it at 90.146.82.82:28035.
How reliable is Testing?
Right now, Testing is up and running. It spent 135 of the last 144 hours online across 6 days, giving 94% uptime. It was first observed by Top Rust Servers on 6 October 2026.
Wipe details
On what schedule does Testing wipe?
Not enough wipe data exists yet to identify the rhythm of Testing. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The present world has been live since 7 days 1 hours ago.
Joining the server
How can I connect to Testing?
To connect, start Rust, hit F1, and enter client.connect 90.146.82.82:28035. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.