TST16013
Test
Offline 185.244.213.67:28015 checked 26d 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
daily · 1 is bestTop 69% 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
newest first| 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.
-
01COMPlayers 533/575
-
02COMPlayers 360/400
-
03COMPlayers 43/250
-
04COMPlayers 39/250
-
05COMPlayers 119/150
-
06COMPlayers 129/200
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry Test?
These Rust Tracker lists carry Test: Community servers, no tags. On the server list, these filters 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 on Test?
The game's server browser reads these tags from Test: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2634 (Protocol): To join, your game must match protocol 2634; cs166494 (Build): This server runs game build 166494; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): The region code is unset. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Schedule
Which wipe times are confirmed for Test?
The record holds too few of Test's wipes to show its rhythm. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. This world has been running 26 days 23 hours.
Server Details
Is Test up, and how does its uptime hold?
Offline now, Test was last seen 26 days 23 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 1 October 2026.
Which Rust build is Test running?
Rust network protocol 2634 and build 166494 on Windows is what Test runs. Steam updates it for you; your game must share the protocol to join.
What location is Test hosted in?
Region: none published by Test. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. Connect on 185.244.213.67:28015.
Player Count
Is Test busy?
Last seen 26 days 23 hours ago; Test is offline at present.
What rank does Test carry among Rust servers?
Seven-day player hours put Test at #16,013, within the top 69% of all ranked servers.
Settings
Which settings and rules are confirmed on Test?
Nothing in Test's name states a gather rate. Up to 8 players per group, the game's default. survival is the game mode, gather, build, raid, as the game intends. Fighting and raiding between players are on. A community server: the server browser lists it under Community. VAC is on, Valve's anti-cheat.
What map is Test on?
Procedural map on Test, made by the game.
How to Join
Which steps join Test?
Open the console in Rust with F1 after starting the game, then type client.connect 185.244.213.67:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8
Game
gmrust
mp10
ts8
v2634
cs166494
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.