Station XX-15282 · no signal
Testing
Offline 185.189.255.113:35300 checked 34d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,282
- top 66%
- Last wipe
- 45d ago
- monthly schedule
- Next wipe
- 6d 18h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 6d 18h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 6d 18hThu 5 Nov, 19:00 UTCFW
- 34d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 19 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 14 Sep, 14:21 UTC45d ago | M0.0▲rising | 1 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Testing?
Generated by the game, the map on Testing is procedural, size 4,250 with seed 121315421. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Testing?
You will find no gather rate in the name of Testing. At the game's default, groups can have up to 8 players. In pve mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Testing right now?
Testing is not responding at this moment and is offline, last seen 34 days 3 hours ago.
How does Testing rank against other Rust servers?
The last seven days of player hours place Testing at #15,282, in the top 66% of all ranked servers.
Operator and location
How reliably does Testing stay online?
As recorded now, Testing is not reachable, the last contact having been 34 days 3 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does Testing run from?
No region is published by Testing. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 185.189.255.113:35300.
What build of Rust does Testing use?
Testing is running Rust network protocol 2633 and build 162929 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Testing?
On average, the busiest point of its recent wipes drew 1 players. 19 hours into the latest wipe, the crowd reached its peak.
How often does Testing wipe, and on which days?
The force wipe is the only wipe Testing takes, once a month. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. The present world dates from 45 days 10 hours. The tags it publishes carry a monthly wipe schedule.
Server tags
What do the server tags on Testing mean?
Tags published by Testing and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): The server has 100 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs162929 (Build): Game build: 162929; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Testing appear?
The Rust Server Trends lists that take in Testing are: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Join the server
What steps get you onto Testing?
Enter client.connect 185.189.255.113:35300 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. For the website, go to https://rustblaze.gamestores.app/.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.