RS-16032Community server
test server
Offline 74.36.211.253:28015 checked 12d 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 69% 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 test server?
test server is offline at this moment; the last signal was 12 days 4 hours ago.
How is test server ranked?
On player hours across seven days, test server is #16,032, inside the top 69% of all ranked servers.
Tags, lists, and filters
On Top Rust Servers, which lists and filters carry test server?
These Top Rust Servers lists count test server among their servers: Best Rust community servers. These filters 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 test server?
Published by test server for the game's server browser to read: gmrust (Game mode): Survival follows the standard Rust ruleset; mp10 (Max players): Player slots: 10; ts8 (Group limit): At most 8 per team, as standard in the game; v2634 (Protocol): To join, your game must be on protocol 2634; cs166494 (Build): Running game build 166494; 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
Which map is running on test server?
test server uses a procedural map, which the game generates.
What settings and rules does test server use?
The name test server does not state a gather rate. The group limit is the game's default of 8 players. survival is the game mode, standard survival: gathering, building and raiding. Combat and raiding between players are allowed. It appears under Community in the server browser and is a community server. The server runs with VAC on.
About the server
What version is test server running?
test server uses Rust network protocol 2634 and build 166494 with Windows as its system. Your game needs the same protocol to connect; Steam takes care of updating it.
What is the location of test server?
No region is published by test server. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. 74.36.211.253:28015 is its address.
What is the uptime of test server?
Currently offline is test server, last seen 12 days 4 hours ago. It spent 0 of the last 168 hours online across 7 days, giving 0% uptime. The first time Top Rust Servers saw it was on 1 October 2026.
Wipe cycle
How often does test server wipe?
Not enough wipe data exists yet to identify the rhythm of test server. The monthly force wipe applies to every Rust server; the next one is on Thursday 5 November at 19:00 UTC. The world it is running now dates from 12 days 4 hours ago.
How to join
What are the steps to join test server?
Use the console: open Rust, press F1, and type client.connect 74.36.211.253:28015. Or simply click Launch Rust here; it opens the game through Steam and connects you.