RUST METRICSFlight deck · live data
Data live Servers11,880 Players98,236 Populated3,914 Fresh wipes 3 h395 Scan5 min
‹ All servers94.214.119.233:28015
Offline Full Queue Fresh wipe Wipe due No query

Custom Map Test

Offline 94.214.119.233:28015 checked 28d ago

COM 1 · connect

Server instruments

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

Players now

10% 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,109top 60%
Last wipe28d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k24 Sep27 Sep30 Sep2 Oct5 Oct8 Oct

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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 11:57 UTC28d ago 1 – running 1

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

What happens on Custom Map Test when wipe day comes?

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

How often does Custom Map Test wipe, and when?

To tell the rhythm of Custom Map Test, 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. 28 days 4 hours ago the current world was made.

Lists and filters

Which tags does Custom Map Test carry, and what do they mean?

These are the tags Custom Map Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Custom Map Test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Custom Map Test: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Custom Map Test hold among Rust servers?

Player hours over seven days put Custom Map Test at #14,109, in the top 60% of all ranked servers.

How full does Custom Map Test get?

Status for Custom Map Test: offline. Last seen 28 days 1 hours ago.

Operator and location

What location is Custom Map Test hosted in?

No region comes from Custom Map Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 94.214.119.233:28015.

What Rust version is Custom Map Test on?

Reading: Custom Map Test, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.

Is Custom Map Test up, and how often does it stay up?

Check: connection. Custom Map Test is offline at this moment. Last contact was 28 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 24 September 2026.

Rules and settings

What settings and rules apply on Custom Map Test?

Reading the name gives no gather rate for Custom Map Test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Join

What do you do to join Custom Map Test?

Check: join. Open Rust, press F1, then enter client.connect 94.214.119.233:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.