RS-14362Community server
TEST
Offline 2.26.17.28:28015 checked 4d 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 64% 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
What is the typical player count on TEST?
TEST is offline at this moment; the last signal was 4 days 4 hours ago. A seven-day average of 1 players was reached, peaking at 1.
Where does TEST sit in the rankings?
The last seven days of player hours place TEST at #14,362, in the top 64% of ranked servers.
Tags, lists, and filters
On Top Rust Servers, which lists and filters carry TEST?
On these Top Rust Servers lists you will find TEST: 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 TEST?
The game's server browser reads the tags that TEST publishes: gmrust (Game mode): Standard survival, as in Rust; mp10 (Max players): Player slots: 10; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): This server runs protocol 2634; match it to connect; cs166652 (Build): Running game build 166652; ptrak (Networking): The network layer is RakNet, which is standard for Rust; $r? (Region code): No region code is assigned. 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?
The name TEST does not state a gather rate. Groups use the default maximum of 8 players. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. It appears under Community in the server browser and is a community server. The server runs with VAC on.
Server info
What version is TEST running?
On Windows, TEST operates Rust network protocol 2634 and build 166652. The protocol must match for you to join; Steam will update your game.
What is the location of TEST?
There is no region published by TEST. Top Rust Servers does not look up where the machine stands; it shows where a server says it is. It answers at 2.26.17.28:28015.
What is the uptime of TEST?
The server TEST is down at the moment, with its last appearance 4 days 4 hours ago. It spent 1 of the last 168 hours online across 7 days, giving 1% uptime. It was first observed by Top Rust Servers on 4 October 2026.
Wipe details
How often does TEST wipe?
Not enough wipe data exists yet to identify the rhythm of TEST. 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 8 days 22 hours ago.
Joining the server
How can I connect to TEST?
To connect manually, open the console with F1 and type client.connect 2.26.17.28:28015. Or click Launch Rust on this page to open Rust through Steam and connect directly.