RUST METRICSFlight deck · live data
Data live Servers11,676 Players50,509 Populated3,178 Fresh wipes 3 h130 Scan5 min
‹ All servers188.75.159.118:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 188.75.159.118:28015 checked 7d ago

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,452top 69%
Last wipe7d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k12 Oct15 Oct18 Oct22 Oct25 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap2.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Wed 21 OctSat 17 OctFri 16 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 16:40 UTC7d ago 0 – running 1
Sat 17 Oct, 23:31 UTC11d ago 1 – 3.7 days 0
Fri 16 Oct, 14:37 UTC12d ago 1 – 1.4 days 0

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 should you expect from wipe day on Test?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

When does Test wipe?

No next wipe can be predicted for Test, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 7 days 16 hours ago.

Tag meanings

How should you read the tags on Test?

Tags published by Test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; v2574 (Protocol): Your game must run protocol 2574 to get in; cs111282 (Build): Game build reading: 111282; ptrak (Networking): Network layer: RakNet, the standard for the game; $rger (Region code): ger is the region code on record; ^o (Oxide): It runs Oxide, also known as 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 Test appear in Rust Metrics lists and filters?

On Rust Metrics, Test sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 2 weeks.

Occupancy

Where does Test sit in the rankings?

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

What is the population on Test?

Reading for Test: offline at this moment; last seen 7 days 16 hours ago.

Server

Where does Test sit?

Reading: location. Test gives no region, with region code ger. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 188.75.159.118:28015.

What Rust version is Test on?

Version check: Rust network protocol 2574 and build 111282 on Windows, run by Test. To get in, your game needs the same protocol; Steam applies the update.

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

Test reports offline. The last reading came 7 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 11 October 2026.

Rules and settings

What settings and rules apply on Test?

No gather rate appears in the name: Test. Check: group limit. None published. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC off, Valve's system.

Which map is live on Test?

The game generates a procedural map for Test.

Connection

How do you connect to Test?

To join: start Rust, press F1 and type client.connect 188.75.159.118:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$rger,v2574,gmrust,cs111282,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
v2574
Protocol Your game must run protocol 2574 to get in.
cs111282
Build Game build reading: 111282.
ptrak
Networking Network layer: RakNet, the standard for the game.
$rger
Region code ger is the region code on record.

Mods and access

^o
Oxide It runs Oxide, also known as 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.