RUST METRICSFlight deck · live data
Data live Servers11,700 Players38,590 Populated2,938 Fresh wipes 3 h91 Scan5 min
‹ All servers175.1.76.16:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalTest

Offline 175.1.76.16:28015 checked 4d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#8,070top 36%
Last wipe4d agono schedule published
Next wipe–too few wipes 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
12.5k5k7.5k10k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

Top 36% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 16:34 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

Reset cycle

What should you expect from wipe day on LocalTest?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

What wipe timing does LocalTest follow?

To tell the rhythm of LocalTest, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 4 days 9 hours ago.

Tag meanings

How should you read the tags on LocalTest?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from LocalTest. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show LocalTest?

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

Player count

What position does LocalTest hold among Rust servers?

Player hours over seven days put LocalTest at #8,070, in the top 36% of all ranked servers.

How full does LocalTest get?

LocalTest is not responding; status offline, last seen 4 days 8 hours ago. Check: players over seven days. Average 1, peak 1.

Operator and location

What location is LocalTest hosted in?

No region tag on LocalTest. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 175.1.76.16:28015.

What Rust version is LocalTest on?

Reading: LocalTest, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

LocalTest reports offline. The last reading came 4 days 8 hours ago. Reading: 5% uptime over the last 5 full days. It was up 6 of 120 hours. Reading: first seen 23 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on LocalTest?

No gather rate appears in the name: LocalTest. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on LocalTest?

Check: map. Procedural, generated by the game, on LocalTest.

How to join

What do you do to join LocalTest?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

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