RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h98 Scan5 min
‹ All servers108.167.80.255:28015
Offline Full Queue Fresh wipe Wipe due No query

big O

Offline 108.167.80.255:28015 checked 7d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

Players now

0% 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 average0peak 1
Rank#14,885top 67%
Last wipe7d 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
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

Top 67% 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 peak1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 03:42 UTC7d ago 1 – 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

Reset cycle

What happens on big O when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does big O follow?

To tell the rhythm of big O, 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. The world it runs now was made 7 days 14 hours ago.

Tag meanings

Which tags does big O carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): 500 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from big O. 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 big O?

On Rust Metrics, big O 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 2 weeks.

Population

What position does big O hold among Rust servers?

Player hours over seven days put big O at #14,885, in the top 67% of all ranked servers.

How full does big O get?

big O is not responding; status offline, last seen 7 days 14 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Operator and location

Which location does big O run from?

Reading: location. big O gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 108.167.80.255:28015.

What Rust version is big O on?

Reading: big O, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on big O, and is it online?

big O reports offline. The last reading came 7 days 14 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. Reading: first seen 21 October 2026, recorded by Rust Metrics.

Settings and map

What rules does big O enforce, and what are its settings?

No gather rate appears in the name: big O. 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. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on big O?

The game generates a procedural map for big O.

Join

How do you connect to big O?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players 500 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.