RUST METRICSFlight deck · live data
Data live Servers11,848 Players93,384 Populated3,880 Fresh wipes 3 h381 Scan5 min
‹ All servers188.18.175.195:28015
Offline Full Queue Fresh wipe Wipe due No query

6767

Offline 188.18.175.195:28015 checked 8d ago

COM 1 · connect

Server instruments

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

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#13,802top 62%
Last wipe8d 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
15k10k15k20k17 Oct19 Oct21 Oct23 Oct25 Oct27 Oct

Top 62% 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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 20:05 UTC8d 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 should you expect from wipe day on 6767?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

When does 6767 wipe?

The rhythm of 6767's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 8 days 18 hours ago.

Tags

Which tags does 6767 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): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from 6767. 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 6767?

These Rust Metrics lists carry 6767: 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; Last wipe: In the last 2 weeks.

Occupancy

What position does 6767 hold among Rust servers?

Player hours over seven days put 6767 at #13,802, in the top 62% of all ranked servers.

What is the population on 6767?

Reading for 6767: offline at this moment; last seen 8 days 17 hours ago.

Server

Where does 6767 sit?

Reading: location. 6767 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 188.18.175.195:28015.

What Rust version is 6767 on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by 6767. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on 6767, and is it online?

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

Rules and settings

How is 6767 configured, and what rules are in force?

Reading the name gives no gather rate for 6767. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on 6767?

The game generates a procedural map for 6767.

Connection

What do you do to join 6767?

Check: join. Open Rust, press F1, then enter client.connect 188.18.175.195: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 The server holds 500 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.