RUST METRICSFlight deck · live data
Data live Servers11,631 Players45,053 Populated3,098 Fresh wipes 3 h93 Scan5 min
‹ All servers2.38.140.75:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 2.38.140.75:28015 checked 22h 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 avg7-day peak
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 average1peak 1
Rank#6,296top 28%
Last wipe4d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75113:0015:0017:0020:0008:0010:00

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
12.5k5k7.5k10k22 Oct23 Oct24 Oct26 Oct27 Oct28 Oct

Top 28% 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 13:24 UTC4d ago 1 – running 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

Wipe schedule

What happens on Test when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Test follow?

The rhythm of Test'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. The world in play was created 4 days 18 hours ago.

Tag meanings

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

These are the tags Test publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Test appear in Rust Metrics lists and filters?

On Rust Metrics, Test 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: 5 or more; Last wipe: In the last week.

Population

Where does Test sit in the rankings?

Player hours over seven days put Test at #6,296, in the top 28% of all ranked servers.

What player count does Test carry?

Test is not responding; status offline, last seen 22 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Check: 48-hour peak. 14:00 UTC, 1 players on average.

Operator and location

Which location does Test run from?

Reading: location. Test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 2.38.140.75:28015.

What Rust version is Test on?

Rust network protocol 2635 and build 168909 on Windows is the build Test runs. 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 22 hours ago. Uptime for the last 5 full days: 19 of 120 hours, or 16%. Reading: first seen 22 October 2026, recorded by Rust Metrics.

Map and rules

What rules does Test enforce, and what are its settings?

No gather rate appears in the name: Test. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Join

What do you do to join Test?

Press F1 in Rust and enter client.connect 2.38.140.75: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?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

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.