Test Server
Key statistics
the figures behind the quote- Players now
- 1/ 50 2% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 1 peak 1
- Rank
- #10,472 top 47%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 4d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 4 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 9 Oct 2026 no hostname published
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 bestTop 47% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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 wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 206 on average | 60/2000 | ▼−18−22.7% | |
| 2 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 203 on average | 197/2000 | ▲+58+41.2% | |
| 3 | 1[PvE]Тульский|Русский|Classic+ИвентыEU · groups of 8+ · monthly · 77 on average | 21/200 | ▼−11−34.4% | |
| 4 | 桃乐丝 PVE - 经济 | 养殖 | 技能 | 钓鱼 | 传奇装EA · groups of 8+ · monthly · 76 on average | 26/100 | ▼−54−67.5% | |
| 5 | [US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 65 on average | 42/200 | ▼−1−1.8% | |
| 6 | Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 64 on average | 43/100 | ▲+10+28.7% |
Quick answers
from the figures on this pageServer Rules
How is Test Server configured in terms of rules and settings?
The name of Test Server carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. It runs pve, no combat against other players. In the server browser it appears under Modded, with plugins or settings that change the game. Oxide plugins are running. VAC is active.
What is the current map on Test Server?
Test Server uses a procedural map, which the game generates.
Activity
What position does Test Server hold in the server rankings?
For the last seven days, Test Server holds rank #10,472 on player hours, in the top 47% of all ranked servers.
What is the population on Test Server?
Right now, Test Server is offline; the last sighting was 4 days 2 hours ago. Average players over seven days: 1; peak: 1.
Wipe Cycle
How often does Test Server wipe?
There are too few wipes on record for Test Server to reveal its rhythm. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 4 days 8 hours.
Server Overview
What is the server location for Test Server?
No region is published by Test Server. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 103.112.71.104:27015.
What Rust version is Test Server running?
Rust network protocol 2634 and build 167398 on Windows is what Test Server runs. Your game needs the same protocol to get in; Steam takes care of the update.
How reliable is Test Server and is it currently online?
Offline at this moment: Test Server. Last seen 4 days 2 hours ago. 4 full days have passed with 3% uptime, 3 of 96 hours. First sighting by Rust Analytics: 9 October 2026.
Tags and Rankings
How should you interpret the tags on Test Server?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp50 (Max players): Slot count: 50; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167398 (Build): Build 167398; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^p (PvE): No fighting between players: the world is the threat; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Test Server publishes. The top of this page and the tags both show its players now, its queue and when its world was made.
Where does Test Server show up in Rust Analytics lists and filters?
On Rust Analytics, Test Server matches these lists: Modded Rust servers and Best Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Connection
What is the process to join Test Server?
Type client.connect 103.112.71.104:27015 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 mp50,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z
Game
gmrust
mp50
ts8
v2634
cs167398
ptrak
$r?
Gameplay
^p
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.