TEST
Offline 94.228.214.27:28015 checked 42d 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.
Map and rules
What settings and rules does TEST run?
You will find no gather rate in the name of TEST. 8 players per group is the default limit. The server runs survival, gather, build and raid: the standard game. PvP and raiding are allowed. It is listed under Community in the server browser and is a community server. VAC is on: Valve's anti-cheat is enabled.
Which map is in use on TEST?
TEST runs a procedural map, which the game generates.
Tags and filters
Where does TEST appear among the Rust Server Index lists and filters?
Filed under these Rust Server Index lists is TEST: Community Rust servers, indexed. Filed under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What is meant by the tags on TEST?
Filed under these tags, as published by TEST and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp1 (Max players): The queue ceiling sits at 1; ts8 (Group limit): Game default applies: teams of up to 8; v2633 (Protocol): Your client must run protocol 2633 to connect; cs163794 (Build): The game build here is 163794; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.
Wipe dates
Which wipe timetable does TEST follow?
TEST's rhythm cannot be told yet: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 42 days 20 hours.
Population
Where does TEST sit in the rankings?
On player hours over seven days, TEST takes #15,521, within the top – of ranked servers.
Is TEST quiet or crowded?
At present TEST is offline; its last sighting was 42 days 19 hours ago.
Server details
What Rust version is TEST on?
Rust network protocol 2633 and build 163794, on Windows, is what TEST runs. Steam keeps your game updated, but the protocol must match for you to join.
Is TEST reachable, and does it stay up?
Last seen 42 days 19 hours ago, TEST is offline right now. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 16 September 2026 it was first seen by Rust Server Index.
Which region is TEST in?
There is no region on record for TEST; it publishes none. Rust Server Index takes the server's word for its location and does not look up the machine's position. Connection details: 94.228.214.27:28015.
Connecting
What is the way onto TEST?
Enter client.connect 94.228.214.27: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 mp1,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp1
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.