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

Gathering Wives

Offline 87.157.119.136:28015 checked 14d ago

COM 1 · connect

Server instruments

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

Players now

10% 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,077top 61%
Last wipe26d 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
15k10k15k20k29 Sep3 Oct7 Oct12 Oct16 Oct20 Oct

Top 61% 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 peak3players, 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 3, 13 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 06:13 UTC26d ago 3 – running 1

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 Gathering Wives when wipe day comes?

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

When does Gathering Wives wipe?

The rhythm of Gathering Wives'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. 26 days 12 hours ago the current world was made.

Tag meanings

Which tags does Gathering Wives carry, and what do they mean?

Tags published by Gathering Wives, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Gathering Wives appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Gathering Wives: 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.

Population

Where does Gathering Wives sit in the rankings?

Player hours over seven days put Gathering Wives at #13,077, in the top 61% of all ranked servers.

What is the population on Gathering Wives?

Status for Gathering Wives: offline. Last seen 14 days 20 hours ago.

Server

Where does Gathering Wives sit?

Reading: location. Gathering Wives gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 87.157.119.136:28015.

What Rust version is Gathering Wives on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by Gathering Wives. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Gathering Wives, and is it online?

Check: connection. Gathering Wives is offline at this moment. Last contact was 14 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 29 September 2026.

Rules and settings

What rules does Gathering Wives enforce, and what are its settings?

Reading the name gives no gather rate for Gathering Wives. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is Gathering Wives on?

Check: map. Procedural, generated by the game, on Gathering Wives.

Connection

How do you connect to Gathering Wives?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.