RUST METRICSFlight deck · live data
Data live Servers11,743 Players54,666 Populated3,375 Fresh wipes 3 h133 Scan5 min
‹ All servers77.240.177.48:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Rust Bot Test

Offline 77.240.177.48: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,232top 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
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 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?

To tell the rhythm of Local Rust Bot Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 18 days ago the current world was made.

Lists and filters

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

Tags published by Local Rust Bot Test, read by the game's server browser: 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): The region field is empty; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?

Rust Metrics lists featuring 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.

Player count

What position does Local Rust Bot Test hold among Rust servers?

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

What is the population on Local Rust Bot Test?

Status for Local Rust Bot Test: offline. Last seen 6 days 18 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

Which location does Local Rust Bot Test run from?

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

What Rust version is Local Rust Bot Test on?

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

Is Local Rust Bot Test up, and how often does it stay up?

Reading: offline. Local Rust Bot Test last answered 6 days 18 hours ago. Uptime for the last 6 full days: 5 of 144 hours, or 3%. The first sighting on Rust Metrics was 21 October 2026.

Map and rules

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

No gather rate appears in the name: Local Rust Bot Test. 8 players per group, the default value. The mode is pve. Note the following: no combat against other players. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Local Rust Bot Test?

Check: map. Procedural, generated by the game, on Local Rust Bot Test.

Join

How do you connect to Local Rust Bot Test?

Press F1 in Rust and enter client.connect 77.240.177.48: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 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 The region field is empty.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

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.