test - Procedural
Offline 186.208.153.100:28015 checked 14d 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 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.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 14 Oct, 17:40 UTC14d ago | 1 | – | running | 1 |
| Wed 14 Oct, 06:41 UTC15d ago | 1 | – | 0.5 days | 0 |
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 - Procedural rank against other Rust servers?
Over the past week it ranks #14,840 for player hours, which puts test - Procedural in the top 69% of all ranked servers.
How busy is test - Procedural?
We have no live count for test - Procedural right now. It was last seen 14 days 12 hours ago.
Tags
What do the server tags on test - Procedural mean?
What the game's server browser reads from test - Procedural is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp2 (Max players): You can join up to 2 slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2634 (Protocol): The protocol is 2634; a different version will not connect; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): Plugins or settings change the game; it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include test - Procedural?
These Rust Population lists include test - Procedural: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more and it will show up.
Wipe schedule
What does wipe day look like on test - Procedural?
Across its recent wipes the busiest crowds averaged 1 players. Peak came 0 hours into the latest wipe.
What is the wipe schedule on test - Procedural?
The record holds too few of test - Procedural's wipes to show a rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. Counted from 14 days 15 hours ago, that is how long the current world has stood.
Map and rules
Which map does test - Procedural run?
test - Procedural uses a map the game generates: procedural.
What are the rules and settings on test - Procedural?
No gather rate appears in the name of test - Procedural. Eight players per group is the default, and it applies here. survival is what it runs, gather, build and raid, as in the standard game. Combat between players, raids included, is permitted. The server browser files it under Modded, where plugins or settings alter the game. Oxide plugins are in use here. The anti-cheat VAC from Valve is disabled.
Server details
Which version of Rust does test - Procedural run?
Rust network protocol 2634 and build 167781 on Windows is what test - Procedural uses. Your game needs the same protocol to join; Steam takes care of updating it.
Is test - Procedural online, and how reliable is it?
Offline at the moment, test - Procedural was last seen 14 days 12 hours ago. Over the last 7 full days, 0 of 168 hours were online, or 0%. It was first seen by Rust Population on 12 October 2026.
Where is test - Procedural located?
A region is not published by test - Procedural. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 186.208.153.100:28015.
Getting in
How do I join test - Procedural?
Open the console with F1 in Rust and enter client.connect 186.208.153.100:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.