RUST METRICSFlight deck · live data
Data live Servers11,716 Players55,754 Populated3,252 Fresh wipes 3 h168 Scan5 min
‹ All servers188.32.107.119:28015
Offline Full Queue Fresh wipe Wipe due No query

Squad 67

Offline 188.32.107.119:28015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 1 /3

Players now

33% 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#13,094top 59%
Last wipe2d 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, measured since 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct29 Oct

Top 59% 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, 4 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 26 Oct, 20:45 UTC2d 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 Squad 67?

At their busiest, its recent wipes drew 1 players on average. 4 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does Squad 67 follow?

Its rhythm cannot be told from the wipes of Squad 67 on record: there are too few. 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 2 days 13 hours ago.

Lists and filters

How should you read the tags on Squad 67?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): Slots: 3; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Squad 67. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Squad 67?

On Rust Metrics, Squad 67 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Population

Where does Squad 67 sit in the rankings?

Player hours over seven days put Squad 67 at #13,094, in the top 59% of all ranked servers.

How full does Squad 67 get?

Squad 67 is not responding; status offline, last seen 2 days 9 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server

Where does Squad 67 sit?

No region comes from Squad 67. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 188.32.107.119:28015.

What Rust version is Squad 67 on?

Rust network protocol 2635 and build 168909 on Windows is the build Squad 67 runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Squad 67, and is it online now?

Check: connection. Squad 67 is offline at this moment. Last contact was 2 days 9 hours ago. Uptime for the last 2 full days: 1 of 48 hours, or 2%. Reading: first seen 26 October 2026, recorded by Rust Metrics.

Map and rules

How is Squad 67 configured, and what rules are in force?

Reading the name gives no gather rate for Squad 67. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on Squad 67?

Size 4,250 and seed 1289664818: the game generates the procedural map on Squad 67 from them. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto Squad 67?

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

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players Slots: 3.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.