RUST METRICSFlight deck · live data
Data live Servers11,686 Players34,855 Populated2,843 Fresh wipes 3 h96 Scan5 min
‹ All servers212.31.110.99:28015
Offline Full Queue Fresh wipe Wipe due No query

oxybool local

Offline 212.31.110.99:28015 checked 19d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,863top 72%
Last wipe19d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 13:33 UTC19d ago 0 – running 0

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 schedule

What happens on oxybool local when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does oxybool local wipe?

The rhythm of oxybool local's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 19 days 13 hours ago.

Tags

How should you read the tags on oxybool local?

These are the tags oxybool local publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): Build 167231; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show oxybool local?

These Rust Metrics lists carry oxybool local: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does oxybool local sit in the rankings?

Player hours over seven days put oxybool local at #15,863, in the top 72% of all ranked servers.

What is the population on oxybool local?

oxybool local is not responding; status offline, last seen 19 days 13 hours ago.

Server

Which location does oxybool local run from?

No region tag on oxybool local. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 212.31.110.99:28015.

What Rust version is oxybool local on?

Rust network protocol 2634 and build 167231 on Windows is the build oxybool local runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on oxybool local, and is it online?

Reading: offline. oxybool local last answered 19 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 9 October 2026.

Map and rules

What settings and rules apply on oxybool local?

Check: gather rate. The name oxybool local does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on oxybool local?

The game generates a procedural map for oxybool local.

Connection

How can you get onto oxybool local?

Press F1 in Rust and enter client.connect 212.31.110.99: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 mp10,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build Build 167231.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.