RS-15497Community server
test
Offline 47.93.210.25:28015 checked 21d 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 67% 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?
Currently, test is offline; the last sighting was 21 days 7 hours ago.
What is the ranking of test?
Ranked #15,497 on seven-day player hours, test is in the top 67% of all ranked servers.
Tags and filters
Where does test appear among the Top Rust Servers lists and filters?
These Top Rust Servers lists count test 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.
How should you read the tags on test?
Published by test for the game's server browser to read: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): There are 50 slots; ts8 (Group limit): 8 per team is the default limit; v2633 (Protocol): To join, your game must be on protocol 2633; cs162929 (Build): Running game build 162929; ptrak (Networking): This uses RakNet, Rust's default network layer; $r? (Region code): Region code not set. Shown at the top of this page, and also in the tags: its players now, its queue, and the time its world was made.
Map and rules
Which map is running on test?
test uses a procedural map, which the game generates.
Which settings and rules apply on test?
No gather rate is given in the name test. Up to 8 players per group, as the game defaults. You play survival, 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.
Server info
What is the Rust version on test?
Rust network protocol 2633 and build 162929 is what test runs, on Windows. Your game needs the same protocol to connect; Steam takes care of updating it.
What is the server location for test?
A region is not published by test. What Top Rust Servers shows is where a server says it is, not where the machine stands, which it does not look up. 47.93.210.25:28015 is its address.
What is the uptime of test?
test is offline now; the last time it was seen was 21 days 7 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 13 September 2026.
Wipe details
On what schedule does test wipe?
Too few wipes are recorded for test to establish a rhythm. Every Rust server is wiped by the force wipe each month; the next occurs on Thursday 5 November at 19:00 UTC. The world it is running now dates from 39 days 20 hours ago.
How to join
How can I connect to test?
To connect manually, open the console with F1 and type client.connect 47.93.210.25:28015. Or click Launch Rust on this page to open Rust through Steam and connect directly.