RS-16013Community server
testserver
Offline 95.27.214.81: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 70% 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.
Player count
How populated is testserver?
testserver is offline at this moment; the last signal was 10 days 9 hours ago.
What is the ranking of testserver?
On player hours across seven days, testserver is #16,013, inside the top 70% of all ranked servers.
Tags, lists, and filters
Where does testserver appear among the Top Rust Servers lists and filters?
These Top Rust Servers lists count testserver among their servers: Best Rust community servers. It appears under these filters 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?
The game's server browser reads the tags that testserver publishes: gmrust (Game mode): Standard survival, as in Rust; mp2 (Max players): There are 2 slots; ts8 (Group limit): 8 per team is the default limit; v2633 (Protocol): Protocol 2633 is required to join; your game must be on the same version; cs163207 (Build): Game build: 163207; 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.
Rules, settings, and map
What map is used on testserver?
testserver uses a procedural map, which the game generates.
What does testserver run for rules and settings?
No gather rate is given in the name testserver. The group limit is the game's default of 8 players. You play survival, standard survival: gathering, building and raiding. Player versus player combat and raiding are enabled. A community server, it is found under the Community tab. VAC anti-cheat is active.
Server info
What is the Rust version on testserver?
testserver uses Rust network protocol 2633 and build 163207 with Windows as its system. Your game needs the same protocol to connect; Steam takes care of updating it.
Where can testserver be found?
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. 95.27.214.81:28015 is its address.
What is the uptime of testserver?
Currently offline is testserver, last seen 10 days 9 hours ago. Across the last 7 full days, it was online for 0 of 168 hours, or 0%. It was first observed by Top Rust Servers on 3 October 2026.
Wipe cycle
On what schedule does testserver wipe?
The record holds too few wipes to determine testserver's pattern. A force wipe happens monthly across all Rust servers; the next is scheduled for Thursday 5 November at 19:00 UTC. The world it is running now dates from 10 days 12 hours ago.
How to join
What is the process to join testserver?
Use the console: open Rust, press F1, and type client.connect 95.27.214.81:28015. Or simply click Launch Rust here; it opens the game through Steam and connects you.