RUST METRICSFlight deck · live data
Data live Servers11,793 Players79,700 Populated3,567 Fresh wipes 3 h247 Scan5 min
‹ All servers185.207.214.206:35555
Offline Full Queue Fresh wipe Wipe due No query

Testing

Offline 185.207.214.206:35555 checked 19d ago

vanillamoddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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,858top 72%
Last wipe24d agono schedule published
Next wipe–no wipe seen yet
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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k5 Oct7 Oct10 Oct12 Oct15 Oct17 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What wipe timing does Testing follow?

To tell the rhythm of Testing, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 24 days 7 hours ago.

Tag meanings

How should you read the tags on Testing?

Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp40 (Max players): Slots: 40; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon from Testing. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Testing?

Rust Metrics lists featuring Testing: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

Where does Testing sit in the rankings?

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

What is the population on Testing?

Reading for Testing: offline at this moment; last seen 19 days 1 hours ago.

Server details

Where does Testing sit?

No region tag on Testing. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 185.207.214.206:35555.

What Rust version is Testing on?

Reading: Testing, Rust network protocol 2634 and build 166652, Linux. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. Testing last answered 19 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 5 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Testing?

Check: gather rate. The name Testing does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Testing?

Check: map. Procedural, size 1,024, seed 78941876, generated by the game on Testing. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name CraggyIsland.

Connection

How can you get onto Testing?

To join: start Rust, press F1 and type client.connect 185.207.214.206:35555. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2634,^z,^y,^v,gmvanilla,cs166652,ts8

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp40
Max players Slots: 40.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.