RUST METRICSFlight deck · live data
Data live Servers11,801 Players73,164 Populated3,682 Fresh wipes 3 h113 Scan5 min
‹ All servers175.1.77.94:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalTest

Offline 175.1.77.94:28015 checked 16d 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 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#13,302top 61%
Last wipe18d 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
15k10k15k20k11 Oct13 Oct14 Oct16 Oct17 Oct19 Oct

Top 61% 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 peak2players, 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 2, 20 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 13:02 UTC18d ago 2 – running 1

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 timing

What should you expect from wipe day on LocalTest?

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

What wipe timing does LocalTest follow?

To tell the rhythm of LocalTest, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 18 days 8 hours ago.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from LocalTest. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does LocalTest appear in Rust Metrics lists and filters?

These Rust Metrics lists carry LocalTest: 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.

Player count

Where does LocalTest sit in the rankings?

Player hours over seven days put LocalTest at #13,302, in the top 61% of all ranked servers.

How full does LocalTest get?

LocalTest is not responding; status offline, last seen 16 days 2 hours ago.

Operator and location

Which location does LocalTest run from?

No region comes from LocalTest. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 175.1.77.94:28015.

What Rust version is LocalTest on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by LocalTest. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. LocalTest last answered 16 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 11 October 2026.

Settings and map

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

Reading the name gives no gather rate for LocalTest. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on LocalTest?

The game generates a procedural map for LocalTest.

Join

What do you do to join LocalTest?

Check: join. Open Rust, press F1, then enter client.connect 175.1.77.94: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?,v2634,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

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