testing
Key statistics
the figures behind the quote- Players now
- 0/ 10 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak 1
- Rank
- #9,715 top 44%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 3d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 6 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 10 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 44% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- usual gap
- 0.9 days between real wipes
- wipe-day peak
- 1 players, last three wipes
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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 11 Oct, 12:33 UTC3d ago | 1 | – | running | 0 |
| Sat 10 Oct, 15:45 UTC4d ago | 1 | – | 0.9 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.
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 | 120/300 | ▲+45+60.4% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 173/225 | ▲+53+43.8% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 89/100 | ▼−2−2.1% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 23/1000 | ▼−38−62.2% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 8/1000 | ▼−11−57.7% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 57/700 | ▼−2−3.4% |
Quick answers
from the figures on this pageMap and Rules
How is testing configured in terms of rules and settings?
No gather rate appears in the name of testing. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. VAC is active.
What is the current map on testing?
The game generates the procedural map on testing.
Activity
What is the rank of testing?
For the last seven days, testing holds rank #9,715 on player hours, in the top 44% of all ranked servers.
How many players does testing have?
0 of 10 slots on testing are filled right now. Average players over seven days: 0; peak: 1.
Wipe Schedule
What happens on wipe day at testing?
The average peak across its recent wipes is 1 players. On the latest wipe, 0 hours after the wipe, the crowd peaked.
When does testing schedule its wipes?
No rhythm can be told for testing yet: too few of its wipes are on record. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. Its world now is 3 days 7 hours old.
Server Details
What is the location of testing?
No region is published by testing. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. You can reach it at 38.130.121.58:28055.
testing is on which Rust version?
The build is Rust network protocol 2634 and build 167781 on Windows, running on testing. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of testing?
Online at this moment: testing. 83% is its uptime for the last 3 full days, 60 of 72 hours. The earliest Rust Analytics saw it was 10 October 2026.
Tags and Rankings
What is the meaning of the tags on testing?
Published by testing for the game's server browser to read: gmvanilla (Game mode): Survival in its vanilla form; mp10 (Max players): Slot count: 10; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): Game build: 167781; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does testing show up in Rust Analytics lists and filters?
On Rust Analytics, testing matches these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Connection
How can I connect to testing?
Type client.connect 38.130.121.58:28055 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 mp10,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^o^z
Game
gmvanilla
mp10
ts8
v2634
cs167781
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.