RUST METRICSFlight deck · live data
Data live Servers11,875 Players97,136 Populated3,915 Fresh wipes 3 h398 Scan5 min
‹ All servers193.179.119.96:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Bot Test

Offline 193.179.119.96:28015 checked 16d 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 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,298top 61%
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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 Oct

Top 61% 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

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

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

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is 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): Modded: plugins or settings depart from the stock game from Local Rust Bot Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

These Rust Metrics lists carry Local Rust Bot Test: Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does Local Rust Bot Test sit in the rankings?

Ranking for Local Rust Bot Test: #13,298 on seven-day player hours, top 61% of all ranked servers.

What is the population on Local Rust Bot Test?

Local Rust Bot Test is not responding; status offline, last seen 16 days 19 hours ago.

Server details

Which location does Local Rust Bot Test run from?

No region tag on Local Rust Bot Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 193.179.119.96: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. Check: protocol. To join, your game must match; Steam handles the update.

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

Local Rust Bot Test reports offline. The last reading came 16 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 12 October 2026, recorded by Rust Metrics.

Map and rules

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

Check: gather rate. The name Local Rust Bot Test does not state one. 8 players per group, the default value. pve, fighting between players is off — that is the game mode. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is off.

What map is Local Rust Bot Test on?

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

Join

What do you do to join Local Rust Bot Test?

Check: join. Open Rust, press F1, then enter client.connect 193.179.119.96:28015. Alternatively, use Launch Rust on this page: Steam opens Rust 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 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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 Modded: plugins or settings depart from the stock 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.