RUST METRICSFlight deck · live data
Data live Servers11,756 Players64,636 Populated3,440 Fresh wipes 3 h196 Scan5 min
‹ All servers114.223.188.52:10241
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 114.223.188.52:10241 checked 8d ago

quad moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,375top 70%
Last wipe27d 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 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 70% of all ranked servers, and #627 of the quad servers (top 76%). 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

What wipe timing does TestServer follow?

The rhythm of TestServer's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 27 days 6 hours ago the current world was made.

Tags

How should you read the tags on TestServer?

Tags published by TestServer, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): Slots: 100; ts4 (Group limit): You may team up with at most 4; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Game build reading: 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does TestServer appear in Rust Metrics lists and filters?

On Rust Metrics, TestServer 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 Oxide ^o; Group limit: Quad.

Population

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #15,375, in the top 70% of all ranked servers. Among servers in quad, it stands at #627.

How full does TestServer get?

Status for TestServer: offline. Last seen 8 days 20 hours ago.

Server

Which location does TestServer run from?

No region tag on TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 114.223.188.52:10241.

What Rust version is TestServer on?

Reading: TestServer, Rust network protocol 2634 and build 167231, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. TestServer last answered 8 days 20 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 20 October 2026.

Rules and settings

How is TestServer configured, and what rules are in force?

Reading the name gives no gather rate for TestServer. Groups stop at 4 players. The label given is quad. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Join

How do you connect to TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167231,ts4,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players Slots: 100.
ts4
Group limit You may team up with at most 4.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Game build reading: 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

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.