Test Server
Offline 109.200.242.137:28015 checked 46d 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 Server run?
You will find no gather rate in the name of Test Server. The default group limit of 8 players applies. The server runs survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. The server browser lists it under Community; it is a community server. VAC is on: Valve's anti-cheat is enabled.
What is the map on Test Server?
A procedural map, generated by the game, is what Test Server runs.
Lists and filters
Where does Test Server appear among the Rust Server Index lists and filters?
These lists on Rust Server Index take Test Server: 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.
Which tags are attached to Test Server, and what do they stand for?
Filed under these tags, as published by Test Server and read by the game's server browser: gmrust (Game mode): Rust survival, as standard; mp500 (Max players): Player cap: 500; ts8 (Group limit): The team limit is 8, as in the standard game; v2633 (Protocol): Your client must run protocol 2633 to connect; cs163794 (Build): It runs build 163794; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): No region code has been set. 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 Server follow?
The record holds too few of Test Server's wipes to tell its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 46 days 16 hours is when its current world was made.
Player counts
Is Test Server quiet or crowded?
At present Test Server is offline; its last sighting was 46 days 8 hours ago.
Server details
What version does Test Server use?
Rust network protocol 2633 and build 163794 on Windows is what you will find on Test Server. The protocol must match before you can join, and Steam takes care of updating it.
Is Test Server reachable, and does it stay up?
Last seen 46 days 8 hours ago, Test Server is offline right now. Of the last 7 full days, 0 of 168 hours were up, 0% of the time. The earliest sighting at Rust Server Index is 13 September 2026.
Where in the world is Test Server hosted?
Test Server 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. You will reach it at 109.200.242.137:28015.
Connecting
What steps lead onto Test Server?
Enter client.connect 109.200.242.137: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 mp500,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp500
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.