TEST
Offline 178.176.186.143:28015 checked 44d 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
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.
Rules and settings
What settings and rules does TEST run?
No gather rate appears in the name TEST. The group limit is 8 players, the game's default. Filed under survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. The server browser lists it under Community; it is a community server. The server has VAC, Valve's anti-cheat, turned on.
Which map is in use on TEST?
A procedural map, generated by the game, is what TEST runs.
Tags
Where does TEST appear among the Rust Server Index lists and filters?
The Rust Server Index lists that include TEST are Community Rust servers, indexed. It appears under the following filters 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 listed for TEST?
The server's own tags are listed here, and the game's server browser reads them: TEST gives gmrust (Game mode): Rust survival, as standard; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams cap at 8, the default setting; v2633 (Protocol): Your client must run protocol 2633 to connect; cs163794 (Build): Build on file: 163794; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipe schedule
Which wipe timetable does TEST follow?
The record holds too few of TEST's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 44 days 4 hours.
Players and ranking
Where does TEST sit in the rankings?
Filed under rankings: #15,468 for TEST on seven-day player hours, top – overall.
How many players are on TEST at the moment?
At present TEST is offline; its last sighting was 44 days 3 hours ago.
Server details
Which Rust build is TEST running?
Rust network protocol 2633 and build 163794 on Windows is what you will find on TEST. To join you need the same protocol; Steam handles the update.
What is the uptime and current status of TEST?
The server is down at this moment; the last sighting of TEST was 44 days 3 hours ago. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 15 September 2026 it was first seen by Rust Server Index.
Which region is TEST in?
TEST gives no region at all. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 178.176.186.143:28015.
Connecting
What steps lead onto TEST?
Enter client.connect 178.176.186.143:28015 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
ts8
v2633
cs163794
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.