RUST METRICSFlight deck · live data
Data live Servers11,814 Players69,594 Populated3,624 Fresh wipes 3 h187 Scan5 min
‹ All servers118.71.21.217:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER

Offline 118.71.21.217:28015 checked 4d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

2% 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 average1peak 1
Rank#8,331top 37%
Last wipe4d 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
12.5k5k7.5k10k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 37% 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 schedule

What wipe timing does TEST SERVER follow?

The rhythm of TEST SERVER's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 4 days 21 hours ago.

Tags

How should you read the tags on TEST SERVER?

Tags published by TEST SERVER, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Check: category. Modded, because plugins or settings alter the 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 TEST SERVER?

Rust Metrics lists featuring 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; Last wipe: In the last week.

Player count

Where does TEST SERVER sit in the rankings?

Player hours over seven days put TEST SERVER at #8,331, in the top 37% of all ranked servers.

How full does TEST SERVER get?

TEST SERVER is not responding; status offline, last seen 4 days 1 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server

What location is TEST SERVER hosted in?

No region tag on TEST SERVER. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 118.71.21.217:28015.

What Rust version is TEST SERVER on?

Reading: TEST SERVER, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on TEST SERVER, and is it online?

Reading: offline. TEST SERVER last answered 4 days 1 hours ago. Uptime for the last 3 full days: 0 of 72 hours, or 0%. The first sighting on Rust Metrics was 25 October 2026.

Settings and map

How is TEST SERVER configured, and what rules are in force?

No gather rate appears in the name: TEST SERVER. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. 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.

Join

How do you connect to TEST SERVER?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.