RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h73 Scan5 min
‹ All servers90.146.82.82:28035
Online Full Queue Fresh wipe Wipe due No query

Testing

Online 90.146.82.82:28035 checked 1h ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
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 1
Rank#15,093top 68%
Last wipe4d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeak
0123419:0004:0013:0023:0008:0017:00

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k6 Oct10 Oct15 Oct19 Oct24 Oct28 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 22:03 UTC4d 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?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 4 hours in.

When does Testing wipe?

The rhythm of Testing's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 4 days 20 hours ago the current world was made.

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): Check: mode. Vanilla survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Testing appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Testing: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Player count

Where does Testing sit in the rankings?

Ranking for Testing: #15,093 on seven-day player hours, top 68% of all ranked servers.

How full does Testing get?

Current headcount on Testing: 0 players, 10 slots available. Seven-day check: 0 players on average. Peak reading: 1.

Server

Which location does Testing run from?

No region comes from Testing. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 90.146.82.82:28035.

What Rust version is Testing on?

Rust network protocol 2635 and build 168909 on Linux is the build Testing runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Testing, and is it online?

Check: connection. Testing is online at this moment. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Check: first contact. Rust Metrics logged it on 6 October 2026.

Map and rules

What rules does Testing enforce, and what are its settings?

Reading the name gives no gather rate for Testing. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Testing?

Check: map. Procedural, generated by the game, on Testing.

How to join

How can you get onto Testing?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

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.