RUST METRICSFlight deck · live data
Data live Servers11,782 Players67,928 Populated3,558 Fresh wipes 3 h196 Scan5 min
‹ All servers86.49.84.105:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Bot Test

Offline 86.49.84.105:28015 checked 15d 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#12,988top 60%
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
15k10k15k20k13 Oct15 Oct16 Oct18 Oct19 Oct21 Oct

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

Reset cycle

What wipe timing does Local Rust Bot Test follow?

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 it runs now was made 18 days 14 hours ago.

Tags

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

These are the tags Local Rust Bot Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^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.

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.

Occupancy

Where does Local Rust Bot Test sit in the rankings?

Player hours over seven days put Local Rust Bot Test at #12,988, in the top 60% of all ranked servers.

What player count does Local Rust Bot Test carry?

Reading for Local Rust Bot Test: offline at this moment; last seen 15 days 2 hours ago.

Server details

What location is Local Rust Bot Test hosted in?

No region tag on Local Rust Bot Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 86.49.84.105:28015.

What Rust version is Local Rust Bot Test on?

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

How reliable is Local Rust Bot Test, and is it online now?

Reading: offline. Local Rust Bot Test last answered 15 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Local Rust Bot Test?

No gather rate appears in the name: Local Rust Bot Test. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: other players are not fought. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC off, Valve's system.

Which map is live on Local Rust Bot Test?

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

How to join

How do you connect to Local Rust Bot Test?

Press F1 in Rust and enter client.connect 86.49.84.105:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Gameplay

^p
PvE Check: mode. PvE, so the world supplies the danger, not other players.

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.