RUST METRICSFlight deck · live data
Data live Servers11,873 Players91,534 Populated3,854 Fresh wipes 3 h380 Scan5 min
‹ All servers185.189.255.113:35300
Offline Full Queue Fresh wipe Wipe due No query

Testing

Offline 185.189.255.113:35300 checked 33d ago

monthly wipes moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,282top 66%
Last wipe45d agomonthly schedule
Next wipe7d 3hThu 5 Nov, 19:00 UTC FW
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep22 Sep25 Sep27 Sep30 Sep2 Oct

Top 66% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 3hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 3hFW

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 19 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 14 Sep, 14:21 UTC45d ago 1 – running 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on Testing when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 19 hours after the wipe, the crowd peaked on the latest wipe.

When does Testing wipe?

With the force wipe, once a month, Testing wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 45 days 1 hours ago. A monthly wipe schedule is published in its tags.

Lists and filters

Which tags does Testing carry, and what do they mean?

These are the tags Testing publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs162929 (Build): The server runs game build 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Testing appear in Rust Metrics lists and filters?

On Rust Metrics, Testing sits in these lists: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Occupancy

What position does Testing hold among Rust servers?

Player hours over seven days put Testing at #15,282, in the top 66% of all ranked servers.

How full does Testing get?

Reading for Testing: offline at this moment; last seen 33 days 18 hours ago.

Operator and location

Where does Testing sit?

No region comes from Testing. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 185.189.255.113:35300.

What Rust version is Testing on?

Rust network protocol 2633 and build 162929 on Windows is the build Testing runs. To get in, your game needs the same protocol; Steam applies the update.

Is Testing up, and how often does it stay up?

Check: connection. Testing is offline at this moment. Last contact was 33 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

What settings and rules apply on Testing?

No gather rate appears in the name: Testing. The group cap is 8 players, which is the default in the game. pve, no combat against other players — that is the game mode. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is Testing on?

From seed 121315421, the game generates the procedural map on Testing. Its size is 4,250. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join Testing?

Press F1 in Rust and enter client.connect 185.189.255.113:35300. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://rustblaze.gamestores.app/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,^m,^p,gmvanilla,cs162929,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs162929
Build The server runs game build 162929.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.