TEST
Offline 139.100.251.67:28015 checked 38d 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.
Settings and map
On TEST, which rules and settings apply?
No gather rate appears in the name TEST. 8 players per group is the default limit. The server runs survival, building, gathering and raiding in the standard game. Fighting and raiding other players is permitted. Filed under Community in the server browser, it is a community server. VAC, Valve's anti-cheat, is disabled.
What is the map on TEST?
Generated by the game, the map is procedural on TEST.
Tags
Which lists and filters on Rust Server Index is TEST filed under?
Filed under these Rust Server Index lists is TEST: Community Rust servers, indexed. These filters on the server list bring it up: 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?
These are the tags TEST publishes; the game's server browser reads this list: gmrust (Game mode): Rust survival, as standard; mp10 (Max players): The queue ceiling sits at 10; ts8 (Group limit): Teams cap at 8, the default setting; v2633 (Protocol): The protocol is 2633; older or newer clients cannot join; cs164530 (Build): The game build here is 164530; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): No region code has been set. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.
Wipes and resets
When does TEST wipe?
TEST's rhythm cannot be told yet: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Its present world dates from 39 days 6 hours.
Players and ranking
How is TEST ranked compared with the rest?
Filed under rankings: #15,027 for TEST on seven-day player hours, top – overall.
Is TEST quiet or crowded?
Filed under offline: TEST, last seen 38 days 14 hours ago.
Operator and status
Which Rust build is TEST running?
Rust network protocol 2633 and build 164530 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?
As of now TEST is offline, with its last appearance 38 days 14 hours ago. Uptime for the last 7 full days came to 0%, 0 hours out of 168. On 18 September 2026 it was first seen by Rust Server Index.
What is the location of TEST?
TEST gives no region at all. What Rust Server Index shows is the stated location, not the machine's actual position, which it does not look up. You will reach it at 139.100.251.67:28015.
How to join
How can you connect to TEST?
Enter client.connect 139.100.251.67: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,cs164530,ts8
Game
gmrust
mp10
ts8
v2633
cs164530
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.