RUST METRICSFlight deck · live data
Data live Servers11,636 Players37,139 Populated2,912 Fresh wipes 3 h58 Scan5 min
‹ All servers178.46.87.102:28015
Offline Full Queue Fresh wipe Wipe due No query

Test server

Offline 178.46.87.102:28015 checked 26d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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#16,275top 69%
Last wipe84d 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 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

Reset cycle

What wipe timing does Test server follow?

The rhythm of Test server'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. 84 days 15 hours ago the current world was made.

Lists and filters

How should you read the tags on Test server?

Tags published by Test server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163207 (Build): Build 163207; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?

On Rust Metrics, Test server sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Where does Test server sit in the rankings?

Player hours over seven days put Test server at #16,275, in the top 69% of all ranked servers.

What is the population on Test server?

Reading for Test server: offline at this moment; last seen 26 days 9 hours ago.

Operator and location

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 178.46.87.102:28015.

What Rust version is Test server on?

Reading: Test server, Rust network protocol 2633 and build 163207, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. Test server last answered 26 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: Test server. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. 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.

How to join

How do you connect to Test server?

Press F1 in Rust and enter client.connect 178.46.87.102: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 mp1,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163207
Build Build 163207.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.