Offline159.195.112.128:28015checked 24d ago
Test
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 bestWipe 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 wipesQuick answers
from the figures on this pageRules and settings
Which rules govern Test?
A gather rate is absent from the name of Test. Up to 8 players per group, which is the game's default. The server runs survival, gather, build, raid: the standard game. PvP and raiding are enabled. Under Community in the server browser, it is a community server. VAC is on, Valve's anti-cheat.
What map is used on Test?
A procedural map, generated by the game, runs on Test.
Tags, lists and filters
Where can Test be found in Rust Player Count lists and filters?
These Rust Player Count lists include Test: Best Rust PvE servers. You can find it on the server list using these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you interpret the tags on Test?
These are the tags Test publishes for the game's server browser: gmrust (Game mode): The usual Rust survival experience; mp2 (Max players): The server has 2 slots; ts8 (Group limit): This uses the default team cap: 8 players; v2633 (Protocol): Your game version needs to be on protocol 2633 to connect; cs163493 (Build): Build number: 163493; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): The region code field is empty. The tags also include its current players, its queue and when its world was made, shown at the top of this page.
Player numbers
How full is Test?
Test is offline at the moment; the last time it was seen was 24 days 12 hours ago.
Where does Test sit in the rankings?
Over the last seven days, Test is #13,268 for player hours, placing it in the top – of ranked servers.
Server information
How reliable is Test, and is it online?
Test is down at the moment and was last seen 24 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. Rust Player Count recorded it for the first time on 19 September 2026.
What Rust version is used on Test?
On Windows, Test runs Rust network protocol 2633 and build 163493. Joining requires the same protocol on your game; Steam updates it for you.
What region does Test serve?
No region is published by Test. Where a server says it is, that is what Rust Player Count shows; it does not check the machine's actual location. You can reach it at 159.195.112.128:28015.
Wipe schedule
What wipe pattern does Test follow?
The rhythm of wipes on Test cannot be told yet, since too few are on record. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe applies to all Rust servers. It has been running its current world for 40 days 15 hours.
How to join
What steps are needed to join Test?
Open the Rust console with F1, then type client.connect 159.195.112.128:28015. Alternatively, fit into the server through the Launch Rust button on this page; that starts Rust via Steam and joins you.
Server tags
what each one meansPublished as mp2,ptrak,$r?,v2633,gmrust,cs163493,ts8
Game
gmrust
mp2
ts8
v2633
cs163493
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.