RUST METRICSFlight deck · live data
Data live Servers11,836 Players72,948 Populated3,667 Fresh wipes 3 h218 Scan5 min
‹ All servers207.177.108.140:28015
Offline Full Queue Fresh wipe Wipe due No query

My Test Server

Offline 207.177.108.140:28015 checked 41d ago

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 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#14,398no region published
Last wipe51d 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. 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 Sep21 Sep22 Sep23 Sep24 Sep
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 schedule

What wipe timing does My Test Server follow?

Its rhythm cannot be told from the wipes of My Test Server on record: there are too few. 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 51 days 15 hours ago.

Tag meanings

Which tags does My Test Server carry, and what do they mean?

Tags published by My Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): Slots: 20; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; 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): Check: framework. Carbon. 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 My Test Server?

Rust Metrics lists featuring My Test Server: 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.

Population

What position does My Test Server hold among Rust servers?

Player hours over seven days put My Test Server at #14,398, in the top – of all ranked servers.

What player count does My Test Server carry?

Reading for My Test Server: offline at this moment; last seen 41 days 13 hours ago.

Operator and location

Where does My Test Server sit?

No region comes from My Test Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 207.177.108.140:28015.

What Rust version is My Test Server on?

Reading: My Test Server, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on My Test Server, and is it online?

Check: connection. My Test Server is offline at this moment. Last contact was 41 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What rules does My Test Server enforce, and what are its settings?

No gather rate appears in the name: My Test Server. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Carbon. Check: anti-cheat. VAC, Valve's system, is off.

What map is My Test Server on?

Procedural map on My Test Server, made by the game's generator.

Connection

How do you connect to My Test Server?

Press F1 in Rust and enter client.connect 207.177.108.140: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?,v2633,gmrust,cs164530,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp20
Max players Slots: 20.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Build 164530.
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 Check: framework. 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.