Test Server
Key statistics
the figures behind the quote- Players now
- 1/ 32 3% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 1 peak 1
- Rank
- #11,451 top 51%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 2d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 32 max players per team
- Gather rate
- – no rate in the name
- Score
- 3 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 21 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 1 players.
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 51% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetWipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 11:11 UTC2d ago | – | – | running | 1 |
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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 127 on average | 184/300 | ▼−28−13.1% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 185/225 | ▼−5−2.8% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 10.10EU · groups of 8+ · weekly · 90 on average | 93/100 | ▲+3+3.7% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 86 on average | 44/1000 | ▼−53−54.6% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 10/1000 | ▼−22−68.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 45/700 | ▼−78−63.4% |
Quick answers
from the figures on this pageRules & Settings
What settings and rules are in place on Test Server?
No gather rate is given in the name of Test Server. The maximum group size is 32 players. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Test Server?
A procedural map runs on Test Server, created by the game.
Activity
What position does Test Server hold in the server rankings?
In the top 51% of all ranked servers, Test Server is #11,451 on player hours over the last seven days.
How full is Test Server?
Right now, Test Server is offline; the last sighting was 46 hours ago. Average players over seven days: 1; peak: 1. At 13:00 UTC in the last 48 hours, it averaged 1 players, the busiest hour.
Wipe Schedule
On what cycle does Test Server wipe?
No rhythm can be told for Test Server yet: too few of its wipes are on record. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 2 days.
Server Info
Where can Test Server be found?
For Test Server, no region is published. Rust Analytics reports the location a server claims, not the machine's actual location. 106.178.130.181:28015 is its address.
Test Server runs which version of Rust?
The version in use at Test Server: Rust network protocol 2634 and build 167584, on Windows. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of Test Server?
No response from Test Server. It was last seen 46 hours ago. 2% is its uptime for the last 7 full days, 3 of 168 hours. First sighting by Rust Analytics: 21 September 2026.
Tags & Filters
How should you interpret the tags on Test Server?
These tags are published by Test Server and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp32 (Max players): It holds 32 slots; ts32 (Group limit): Team size caps at 32; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167584 (Build): It runs build 167584; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): The region code is absent; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does Test Server show up in Rust Analytics lists and filters?
These Rust Analytics lists include Test Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How to Join
What steps do I take to join Test Server?
Type client.connect 106.178.130.181:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp32,ptrak,$r?,v2634,gmrust,cs167584,ts32,^o^z
Game
gmrust
mp32
ts32
v2634
cs167584
ptrak
$r?
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.