RUST METRICSFlight deck · live data
Data live Servers11,646 Players42,725 Populated3,027 Fresh wipes 3 h89 Scan5 min
‹ All servers213.175.37.210:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Bot Test

Offline 213.175.37.210:28015 checked 6d ago

moddedoxidepve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#9,454top 42%
Last wipe18d agono schedule published
Next wipe–no wipe 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.5k10k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 42% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does Local Rust Bot Test wipe?

Its rhythm cannot be told from the wipes of Local Rust Bot Test on record: there are too few. 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 18 days 9 hours ago.

Tag meanings

How should you read the tags on Local Rust Bot Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server from Local Rust Bot Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Local Rust Bot Test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Local Rust Bot Test: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does Local Rust Bot Test sit in the rankings?

Player hours over seven days put Local Rust Bot Test at #9,454, in the top 42% of all ranked servers.

What player count does Local Rust Bot Test carry?

Local Rust Bot Test is not responding; status offline, last seen 6 days 18 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

What location is Local Rust Bot Test hosted in?

No region tag on Local Rust Bot Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 213.175.37.210:28015.

What Rust version is Local Rust Bot Test on?

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

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

Reading: offline. Local Rust Bot Test last answered 6 days 18 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. Check: first contact. Rust Metrics logged it on 22 October 2026.

Settings and map

How is Local Rust Bot Test configured, and what rules are in force?

No gather rate appears in the name: Local Rust Bot Test. The group cap is 8 players, which is the default in the game. pve, fighting between players is off — that is the game mode. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is off. That is Valve's anti-cheat.

Which map is live on Local Rust Bot Test?

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

Join

What do you do to join Local Rust Bot Test?

To join: start Rust, press F1 and type client.connect 213.175.37.210:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,^p,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Gameplay

^p
PvE There is no player-on-player combat here; the danger comes from the world.

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.