Test
Offline 37.45.52.143:28015 checked 16d 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 63% 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.
Rules and settings
On Test, which rules and settings apply?
The name of Test does not state a gather rate. The default group limit of 8 players applies. Filed under survival, gather, build and raid: the standard game. Combat and raiding between players are possible. The server browser lists it under Community; it is a community server. The server has VAC, Valve's anti-cheat, turned on.
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. 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): Survival on standard Rust rules; mp2 (Max players): The queue ceiling sits at 2; ts8 (Group limit): Game default applies: teams of up to 8; v2634 (Protocol): The protocol is 2634; older or newer clients cannot join; cs167584 (Build): Build on file: 167584; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): A region code is absent. The top of this page shows three items from the tags: players at present, queue and world creation time.
Wipe dates
Which wipe timetable does Test follow?
The record holds too few of Test'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. 16 days 10 hours is when its current world was made.
Population
What position does Test hold among Rust servers?
Filed under rankings: #13,875 for Test on seven-day player hours, top 63% overall.
Is Test quiet or crowded?
At present Test is offline; its last sighting was 16 days 9 hours ago.
Server details
Which Rust build is Test running?
Rust network protocol 2634 and build 167584 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?
Last seen 16 days 9 hours ago, Test is offline right now. Uptime for the last 7 full days came to 0%, 0 hours out of 168. The earliest sighting at Rust Server Index is 12 October 2026.
What is the location of Test?
No region is published by Test. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 37.45.52.143:28015.
Joining the server
How can you connect to Test?
If you would rather use the console, press F1 in Rust and enter client.connect 37.45.52.143:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.
Server tags
What each one means.
Published as mp2,ptrak,$r?,v2634,gmrust,cs167584,ts8
Game
gmrust
mp2
ts8
v2634
cs167584
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.