RS-13897Community server
TestServer
Offline 88.153.199.187:28015 checked 10d 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 61% 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
What is the typical player count on TestServer?
TestServer is offline at this moment; the last signal was 10 days 18 hours ago.
Where does TestServer sit in the rankings?
Ranked #13,897 on seven-day player hours, TestServer is in the top 61% of all ranked servers.
Tags and filters
On Top Rust Servers, which lists and filters carry TestServer?
These Top Rust Servers lists count TestServer among their servers: Best Rust community servers. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on TestServer?
Published by TestServer for the game's server browser to read: gmrust (Game mode): Standard survival, as in Rust; mp5 (Max players): There are 5 slots; ts8 (Group limit): At most 8 per team, as standard in the game; v2634 (Protocol): To join, your game must be on protocol 2634; cs166652 (Build): Running game build 166652; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): No region code is assigned. The top of this page also shows the time its world was made, its queue, and its players now, all from the tags.
Map and rules
Which map is running on TestServer?
A procedural map, created by the game, is in use on TestServer.
What does TestServer run for rules and settings?
The name TestServer does not state a gather rate. The group limit is the game's default of 8 players. You play survival, the normal mode where you gather, build and raid. Combat and raiding between players are allowed. A community server, it is found under the Community tab. VAC, Valve's anti-cheat, is enabled.
Server info
What Rust version is TestServer on?
Rust network protocol 2634 and build 166652 is what TestServer runs, on Windows. Joining requires matching protocols, and Steam updates your game automatically.
What is the location of TestServer?
A region is not published by TestServer. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. It answers at 88.153.199.187:28015.
How reliable is TestServer?
The server TestServer is down at the moment, with its last appearance 10 days 18 hours ago. Across the last 7 full days, it was online for 0 of 168 hours, or 0%. Its first appearance in Top Rust Servers was on 3 October 2026.
Wipe schedule
How often does TestServer wipe?
Not enough wipe data exists yet to identify the rhythm of TestServer. 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 10 days 18 hours ago.
Connection
What is the process to join TestServer?
To connect, start Rust, hit F1, and enter client.connect 88.153.199.187:28015. You can also join by clicking Launch Rust here, which opens Rust through Steam and links you in.