RUST METRICSFlight deck · live data
Data live Servers11,789 Players63,543 Populated3,532 Fresh wipes 3 h121 Scan5 min
‹ All servers68.103.106.192:38015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 68.103.106.192:38015 checked 23d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,982top 71%
Last wipe33d 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
15k10k15k20k1 Oct3 Oct5 Oct8 Oct10 Oct12 Oct

Top 71% 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

How often does Test Server wipe, and when?

To tell the rhythm of Test Server, 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 33 days 12 hours ago.

Lists and filters

How should you read the tags on Test Server?

These are the tags Test Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166722 (Build): Build 166722; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Test Server appear in Rust Metrics lists and filters?

On Rust Metrics, Test Server sits in these lists: 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 Test Server hold among Rust servers?

Ranking for Test Server: #15,982 on seven-day player hours, top 71% of all ranked servers.

What is the population on Test Server?

Status for Test Server: offline. Last seen 23 days 8 hours ago.

Server

Which location does Test Server run from?

Reading: location. Test Server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 68.103.106.192:38015.

What Rust version is Test Server on?

Reading: Test Server, Rust network protocol 2634 and build 166722, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Test Server up, and how often does it stay up?

Test Server reports offline. The last reading came 23 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.

Settings and map

How is Test Server configured, and what rules are in force?

Reading the name gives no gather rate for Test Server. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

What map is Test Server on?

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

Connection

How do you connect to Test Server?

Press F1 in Rust and enter client.connect 68.103.106.192:38015. 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 mp50,ptrak,$r?,v2634,gmrust,cs166722,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166722
Build Build 166722.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the 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.