RUST METRICSFlight deck · live data
Data live Servers11,909 Players102,314 Populated3,972 Fresh wipes 3 h409 Scan5 min
‹ All servers185.215.184.188:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Test 4000

Offline 185.215.184.188: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#7,167top 32%
Last wipe3d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct29 Oct

Top 32% 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.

usual gap0.7 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Mon 26 OctSun 25 Oct
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
Mon 26 Oct, 10:22 UTC3d ago 1 – running 1
Sun 25 Oct, 17:16 UTC4d ago 1 – 0.7 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 Local Rust Test 4000?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Local Rust Test 4000 wipe, and when?

Its rhythm cannot be told from the wipes of Local Rust Test 4000 on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 3 days 7 hours ago the current world was made.

Tag meanings

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

These are the tags Local Rust Test 4000 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (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.

Which lists and filters on Rust Metrics show Local Rust Test 4000?

These Rust Metrics lists carry Local Rust Test 4000: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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 Local Rust Test 4000 hold among Rust servers?

Player hours over seven days put Local Rust Test 4000 at #7,167, in the top 32% of all ranked servers.

How full does Local Rust Test 4000 get?

Reading for Local Rust Test 4000: offline at this moment; last seen 43 hours ago. Seven-day check: 1 players on average. Peak reading: 1. Average at the busiest hour was 1 players, at 22:00 UTC over the last 48 hours.

Server details

What location is Local Rust Test 4000 hosted in?

No region comes from Local Rust Test 4000. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.215.184.188:28015.

What Rust version is Local Rust Test 4000 on?

Rust network protocol 2635 and build 168909 on Windows is the build Local Rust Test 4000 runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. Local Rust Test 4000 is offline at this moment. Last contact was 43 hours ago. Reading: 28% uptime over the last 3 full days. It was up 20 of 72 hours. The first sighting on Rust Metrics was 25 October 2026.

Rules and settings

What settings and rules apply on Local Rust Test 4000?

No gather rate appears in the name: Local Rust Test 4000. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is Local Rust Test 4000 on?

The game generates a procedural map for Local Rust Test 4000.

Connection

How do you connect to Local Rust Test 4000?

Check: join. Open Rust, press F1, then enter client.connect 185.215.184.188: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 Slots: 50.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (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.