RUST METRICSFlight deck · live data
Data live Servers11,748 Players75,412 Populated3,731 Fresh wipes 3 h136 Scan5 min
‹ All servers180.112.65.104:10241
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 180.112.65.104:10241 checked 14d 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,346top 71%
Last wipe26d 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 71% of all ranked servers, and #608 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 schedule

How often does TestServer wipe, and when?

The rhythm of TestServer's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 26 days 8 hours ago the current world was made.

Tags

How should you read the tags on TestServer?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts4 (Group limit): Teams are capped at 4; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Build 167231; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from TestServer. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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.

Occupancy

Where does TestServer sit in the rankings?

Ranking for TestServer: #15,346 on seven-day player hours, top 71% of all ranked servers. The quad group places it at #608.

What player count does TestServer carry?

TestServer is not responding; status offline, last seen 14 days 22 hours ago.

Server details

What location is TestServer hosted in?

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

What Rust version is TestServer on?

Rust network protocol 2634 and build 167231 on Windows is the build TestServer runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. TestServer last answered 14 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 October 2026.

Rules and settings

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

Reading the name gives no gather rate for TestServer. The group cap is 4 players, read as quad. 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. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Connection

What do you do to join TestServer?

Press F1 in Rust and enter client.connect 180.112.65.104:10241. 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 mp100,ptrak,$r?,v2634,gmrust,cs167231,ts4,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts4
Group limit Teams are capped at 4.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Build 167231.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the 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.