RUST METRICSFlight deck · live data
Data live Servers11,713 Players43,388 Populated3,068 Fresh wipes 3 h103 Scan5 min
‹ All servers176.226.131.153:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Test 4000

Offline 176.226.131.153:28015 checked 1d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% 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,810top 40%
Last wipe2d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75117:0018:0020:0021:0023:0000: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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 10:22 UTC2d ago 1 – 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 schedule

What should you expect from wipe day on Local Rust Test 4000?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 7 hours in.

What wipe timing does Local Rust Test 4000 follow?

The rhythm of Local Rust Test 4000's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 2 days 14 hours ago.

Tags

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

Tags published by Local Rust Test 4000, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^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 Local Rust Test 4000?

Rust Metrics lists featuring Local Rust Test 4000: 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 3 days.

Population

Where does Local Rust Test 4000 sit in the rankings?

Player hours over seven days put Local Rust Test 4000 at #8,810, in the top 40% of all ranked servers.

How full does Local Rust Test 4000 get?

Status for Local Rust Test 4000: offline. Last seen 24 hours ago. Seven-day check: 1 players on average. Peak reading: 1. The last 48 hours peaked at 19:00 UTC, averaging 1 players at that hour.

Server details

Where does Local Rust Test 4000 sit?

No region tag on Local Rust Test 4000. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 176.226.131.153:28015.

What Rust version is Local Rust Test 4000 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by Local Rust Test 4000. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on Local Rust Test 4000, and is it online?

Reading: offline. Local Rust Test 4000 last answered 24 hours ago. Uptime for the last 3 full days: 11 of 72 hours, or 15%. Check: first contact. Rust Metrics logged it on 25 October 2026.

Rules and settings

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

No gather rate appears in the name: Local Rust Test 4000. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Local Rust Test 4000?

Procedural map on Local Rust Test 4000, made by the game's generator.

Connection

What do you do to join Local Rust Test 4000?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.