Test
Offline 31.162.18.183:28015 checked 8d ago
Measurements
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Monday 2 November, 18:37 UTC, in 5d 13h. Biweekly: 14 days after its last 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.
Quick answers
Player counts
How does Test rank against other Rust servers?
Over the past week it ranks #15,322 for player hours, which puts Test in the top 70% of all ranked servers.
How busy is Test?
We have no live count for Test right now. It was last seen 8 days 10 hours ago.
Tags
What do the server tags on Test mean?
The game's server browser reads the tags Test publishes: gmvanilla (Game mode): The game mode is vanilla survival; mp200 (Max players): The server has 200 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2634 (Protocol): The protocol is 2634; a different version will not connect; cs167781 (Build): This server runs game build 167781; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): This server has no region code; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): Players do not fight each other; the world supplies the danger; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): The game is changed by plugins or settings, so it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.
Which Rust Population lists and filters include Test?
Test appears among the Rust Population lists that follow: Modded Rust servers, counted and PvE servers, counted. Filter the server list by Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks and it will show up.
Wipe notes
What is the wipe schedule on Test?
An estimate from biweekly: 14 days after its last wipe gives Test's next wipe. A wipe is due on Monday 2 November at 18:37 UTC, the next one. The world it runs now dates from 8 days 10 hours ago. A wipe every two weeks is what the tags publish.
Map and rules
Which map does Test run?
Test uses a map the game generates: procedural.
What are the rules and settings on Test?
No gather rate appears in the name of Test. The group limit is 8 players, which is the default. This server runs pve, no player combat. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. The anti-cheat VAC from Valve is enabled.
Server details
Which version of Rust does Test run?
Rust network protocol 2634 and build 167781 on Windows is what Test uses. Your game needs the same protocol to join; Steam takes care of updating it.
Is Test online, and how reliable is it?
Currently offline, Test was last seen 8 days 10 hours ago. Over the last 7 full days, 0 of 168 hours were online, or 0%. The first sighting by Rust Population was on 19 October 2026.
Where is Test located?
Nothing published by Test states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 31.162.18.183:28015.
How to join
How do I join Test?
Open the console with F1 in Rust and enter client.connect 31.162.18.183:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.