RUST METRICSFlight deck · live data
Data live Servers11,805 Players79,944 Populated3,786 Fresh wipes 3 h105 Scan5 min
‹ All servers138.2.234.74:28015
Offline Full Queue Fresh wipe Wipe due No query

GameOps Rust

Offline 138.2.234.74:28015 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,101top 70%
Last wipe12d 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
15k10k15k20k15 Oct16 Oct18 Oct19 Oct21 Oct22 Oct

Top 70% 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
Thu 15 Oct, 16:18 UTC13d 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 timing

What happens on GameOps Rust 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 GameOps Rust wipe?

The rhythm of GameOps Rust'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. 12 days 22 hours ago the current world was made.

Tag meanings

How should you read the tags on GameOps Rust?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from GameOps Rust. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does GameOps Rust appear in Rust Metrics lists and filters?

These Rust Metrics lists carry GameOps Rust: 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 GameOps Rust hold among Rust servers?

Player hours over seven days put GameOps Rust at #15,101, in the top 70% of all ranked servers.

What player count does GameOps Rust carry?

Reading for GameOps Rust: offline at this moment; last seen 12 days 22 hours ago.

Operator and location

Which location does GameOps Rust run from?

Reading: location. GameOps Rust gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 138.2.234.74:28015.

What Rust version is GameOps Rust on?

Rust network protocol 2634 and build 167781 on Linux is the build GameOps Rust runs. To get in, your game needs the same protocol; Steam applies the update.

Is GameOps Rust up, and how often does it stay up?

Check: connection. GameOps Rust is offline at this moment. Last contact was 12 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does GameOps Rust enforce, and what are its settings?

Check: gather rate. The name GameOps Rust does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — 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. VAC is on. That is Valve's anti-cheat.

What map is GameOps Rust on?

Procedural map on GameOps Rust, made by the game's generator.

Connection

How can you get onto GameOps Rust?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players Slots: 50.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.