Testing
Online 90.146.82.82:28035 checked 9m ago
Vital stats
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 68% 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 22:03 UTC4d ago | 1 | – | running | 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.
Quick answers
From the figures on this page.
Tags
Which Rust Pop Watch lists and filters include Testing?
These Rust Pop Watch lists include Testing: Modded Rust servers, live. These filters 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 week.
What do the server tags on Testing mean?
The game's server browser picks up these tags from Testing: gmvanilla (Game mode): This is vanilla survival; mp10 (Max players): There are 10 slots; ts8 (Group limit): The default team size of 8 applies here; v2635 (Protocol): You need the same game version to get in: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region is listed; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon, a plugin framework, is what it runs. Current players, queue and world age are in the tags too, displayed at the top of this page.
Player counts
How does Testing rank against other Rust servers?
A seven-day player-hours placing of #14,994 puts Testing in the top 68% of all ranked servers.
How many players are on Testing right now?
The current tally at Testing: 0 players across 10 slots. Peak for the week was 1, against an average of 0 players.
Server facts
Is Testing online, and how reliable is it?
Right now, Testing is up and running. Out of 168 hours in the last 7 full days, it was online for 168, a 100% uptime. It came to Rust Pop Watch's attention on 6 October 2026.
Where is Testing located?
No region is published by Testing. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. Connect at 90.146.82.82:28035.
Which Rust version is Testing on?
Rust network protocol 2635 and build 168909 is the version Testing runs on Linux. Joining requires your game to match the protocol, which Steam updates for you.
The wipe schedule
What happens on Testing when wipe day comes around?
Recent wipes averaged a peak of 1 players at their busiest. The crowd on the latest wipe topped out 4 hours in.
What is the wipe schedule on Testing?
Too few wipes are on record for Testing to reveal its rhythm. On Thursday 5 November at 19:00 UTC the force wipe arrives, and every Rust server wipes with it at monthly intervals. Its current world has been live for 4 days 22 hours.
Rules and settings
Which map does Testing run?
The map on Testing is procedural, made by the game.
What are the rules and settings on Testing?
No gather rate appears in the name of Testing. The group limit is 8 players, the game's default. It runs survival, the usual game of gathering, building and raiding. Players can raid and fight one another. The server browser files it under Modded, where plugins or settings change the game. The plugin count is Carbon. The VAC anti-cheat from Valve is on.
Getting in
How do I join Testing?
Enter client.connect 90.146.82.82:28035 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically.