RUST METRICSFlight deck · live data
Data live Servers11,722 Players61,093 Populated3,368 Fresh wipes 3 h184 Scan5 min
‹ All servers179.64.109.233:28015
Offline Full Queue Fresh wipe Wipe due No query

testing

Offline NA 179.64.109.233:28015 checked 6d ago

duo weekly wipes moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 1 /20

Players now

5% 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#12,664top 57% · #1385 in NA
Last wipe18d agoweekly schedule
Next wipe2d 4hSat 31 Oct, 15:49 UTC
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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 57% of all ranked servers, top 74% in NA, and #350 of the duo servers (top 83%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Next wipe Saturday 31 October, 15:49 UTC, in 2d 4h. Weekly: 7 days after its last 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 schedule

How often does testing wipe, and when?

An estimate from weekly: 7 days after its last wipe gives testing's next wipe. Saturday 31 October at 15:49 UTC is when its next wipe is due. 18 days 19 hours ago the current world was made. Its tags carry a weekly wipe schedule.

Lists and filters

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

Tags published by testing, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp20 (Max players): The server holds 20 slots; ts2 (Group limit): Team cap: 2; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^w (Weekly): Check: wipe cycle. Every week; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon; NA (North America): North America is the browser category it sits in. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does testing appear in Rust Metrics lists and filters?

Rust Metrics lists featuring testing: Duo Rust servers, Modded Rust servers, checked live and North America: server readout. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Duo; Wipe schedule: Weekly.

Player count

Where does testing sit in the rankings?

Player hours over the last seven days put testing at #12,664, #1,385 in North America, in the top 57% of all ranked servers. Among servers in duo, it stands at #350.

What player count does testing carry?

Reading for testing: offline at this moment; last seen 6 days 3 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

What location is testing hosted in?

Reading: location. The NA tag puts testing in North America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 179.64.109.233:28015.

What Rust version is testing on?

Rust network protocol 2635 and build 168909 on Windows is the build testing runs. Matching protocol is required to join. Let Steam update your game.

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

testing reports offline. The last reading came 6 days 3 hours ago. Uptime for the last 6 full days: 2 of 144 hours, or 1%. The first sighting on Rust Metrics was 22 October 2026.

Rules and settings

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

No gather rate appears in the name: testing. Groups stop at 2 players. The label given is duo. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Check: anti-cheat. VAC, Valve's system, is on.

Join

How do you connect to testing?

Press F1 in Rust and enter client.connect 179.64.109.233:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2635,^z,^y,^w,NA,gmvanilla,cs168909,ts2

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp20
Max players The server holds 20 slots.
ts2
Group limit Team cap: 2.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Check: wipe cycle. Every week.

Mods and access

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

Region

NA
North America North America is the browser category it sits in.

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.