solo testing
Offline 216.16.101.189:28015 checked 1d ago
Measurements
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 31% 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.
Quick answers
Player counts
How does solo testing rank against other Rust servers?
The last seven days of player hours place solo testing at #6,837, within the top 31% of all ranked servers.
How busy is solo testing?
At this count solo testing is offline, with its last sighting 34 hours ago. Averaged over seven days, it drew 1 players and reached a peak of 1. In the last 48 hours the peak hour came at 04:00 UTC, averaging 1 players.
Lists and tags
What do the server tags on solo testing mean?
What the game's server browser reads from solo testing is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server has no region code. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include solo testing?
These Rust Population lists include solo testing: Community servers, field-listed. These are the filters it appears under when you browse the list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Wipe notes
What is the wipe schedule on solo testing?
The record holds too few of solo testing's wipes to show a rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 12 days 15 hours ago, that is how long the current world has stood.
Settings
Which map does solo testing run?
solo testing uses a map the game generates: procedural.
What are the rules and settings on solo testing?
The name tells you nothing about gather rates: solo testing states none. Eight players per group is the default, and it applies here. This server runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players is allowed. You will find it under Community: it is a community server. The anti-cheat VAC from Valve is enabled.
About the server
Which version of Rust does solo testing run?
The setup is Rust network protocol 2635 and build 168909 on Windows for solo testing. Steam updates your game automatically, but you need the same protocol to join.
Is solo testing online, and how reliable is it?
Offline at the moment, solo testing was last seen 34 hours ago. It was up 15% of the time over the last 7 full days, 26 out of 168 hours. On 17 October 2026, Rust Population saw it for the first time.
Where is solo testing located?
No region is published by solo testing. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 216.16.101.189:28015.
How to join
How do I join solo testing?
To connect directly, open Rust's console with F1 and type client.connect 216.16.101.189:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.