Offline13.143.140.3:28015checked 30d 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 pageSettings and map
Which rules govern Test?
The name of Test does not state a gather rate. No group limit is published. The server runs survival, gather, build, raid: the standard game. Fighting and raiding between players is allowed. The server browser lists it as Modded, with plugins or settings that alter the game. Oxide plugins are running on it. Anti-cheat VAC from Valve is on.
What is the map on Test?
A procedural map is what Test runs, generated by the game.
Server tags
Where can Test be found in Rust Player Count lists and filters?
The Rust Player Count lists that Test fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o.
How should you interpret the tags on Test?
The game's server browser reads these tags from Test: gmrust (Game mode): The usual Rust survival experience; mp1 (Max players): 1 slots are available; v2556 (Protocol): To join, your game must match protocol 2556; cs104046 (Build): It runs on game build 104046; ptrak (Networking): It uses RakNet, the game's default networking; $rpol (Region code): Region code set to pol; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded category: plugins or configuration change gameplay. At the top of this page, its tags show its current players, queue and world creation time as well.
Population
How many players does Test have?
Test is offline at the moment; the last time it was seen was 30 days 13 hours ago.
About the server
What is the online status and reliability of Test?
Test is down at the moment and was last seen 30 days 13 hours ago. For the last 7 full days, it was online for 0 of 168 hours, a 0% uptime. 13 September 2026 is when Rust Player Count first saw it.
What is the Rust version for Test?
On Windows, Test runs Rust network protocol 2556 and build 104046. Joining requires the same protocol on your game; Steam updates it for you.
What region does Test serve?
No region is published by Test, and the region code is pol. Where a server says it is, that is what Rust Player Count shows; it does not check the machine's actual location. It is located at 13.143.140.3:28015.
Wipe information
When does Test wipe?
Too few wipes are recorded for Test to reveal its pattern. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe applies to all Rust servers. The present world dates from 48 days 15 hours ago.
Join the server
What is the process to join Test?
Joining is done by opening the console (F1) and running client.connect 13.143.140.3:28015. Another way is the Launch Rust option on this page, which uses Steam to start Rust and put you in.
Server tags
what each one meansPublished as mp1,ptrak,$rpol,v2556,gmrust,cs104046,^o^z
Game
gmrust
mp1
v2556
cs104046
ptrak
$rpol
Mods and access
^o
^z
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.