RUST METRICSFlight deck · live data
Data live Servers11,705 Players41,937 Populated3,034 Fresh wipes 3 h101 Scan5 min
‹ All servers86.106.182.68:28135
Offline Full Queue Fresh wipe Wipe due No query

bro-oxsave

Offline 86.106.182.68:28135 checked 3d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

Players now

0% 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#15,349top 69%
Last wipe4d 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
15k10k15k20k24 Oct25 Oct26 Oct27 Oct28 Oct29 Oct

Top 69% 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 bro-oxsave follow?

The rhythm of bro-oxsave's wipes cannot be told yet: too few are on record. 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 4 days 8 hours ago.

Tag meanings

How should you read the tags on bro-oxsave?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from bro-oxsave. 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 bro-oxsave?

On Rust Metrics, bro-oxsave sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

Where does bro-oxsave sit in the rankings?

Ranking for bro-oxsave: #15,349 on seven-day player hours, top 69% of all ranked servers.

What player count does bro-oxsave carry?

bro-oxsave is not responding; status offline, last seen 3 days 21 hours ago. A seven-day average of 0 players is the reading.

Operator and location

What location is bro-oxsave hosted in?

No region tag on bro-oxsave. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 86.106.182.68:28135.

What Rust version is bro-oxsave on?

Reading: bro-oxsave, Rust network protocol 2634 and build 167781, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is bro-oxsave, and is it online now?

bro-oxsave reports offline. The last reading came 3 days 21 hours ago. Reading: 1% uptime over the last 4 full days. It was up 1 of 96 hours. The first sighting on Rust Metrics was 24 October 2026.

Rules and settings

What rules does bro-oxsave enforce, and what are its settings?

No gather rate appears in the name: bro-oxsave. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is bro-oxsave on?

The game generates a procedural map for bro-oxsave.

How to join

How can you get onto bro-oxsave?

Check: join. Open Rust, press F1, then enter client.connect 86.106.182.68:28135. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.