RUST METRICSFlight deck · live data
Data live Servers11,737 Players52,204 Populated3,347 Fresh wipes 3 h125 Scan5 min
‹ All servers176.100.37.157:28015
Offline Full Queue Fresh wipe Wipe due No query

Anchor Community

Offline 176.100.37.157:28015 checked 6d ago

COM 1 · connect

Server instruments

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

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,344top 69%
Last wipe9d 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 18 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
15k10k15k20k18 Oct20 Oct22 Oct24 Oct26 Oct28 Oct

Top 69% 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 peak10players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 19 Oct, 13:37 UTC9d ago 10 – 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 schedule

What should you expect from wipe day on Anchor Community?

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

How often does Anchor Community wipe, and when?

To tell the rhythm of Anchor Community, too few of its wipes 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 9 days 10 hours ago.

Lists and filters

Which tags does Anchor Community carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Anchor Community. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Anchor Community appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Anchor Community: 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 2 weeks.

Population

Where does Anchor Community sit in the rankings?

Player hours over seven days put Anchor Community at #15,344, in the top 69% of all ranked servers.

What player count does Anchor Community carry?

Anchor Community is not responding; status offline, last seen 6 days 11 hours ago. A seven-day average of 0 players is the reading.

Server

Where does Anchor Community sit?

No region tag on Anchor Community. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 176.100.37.157:28015.

What Rust version is Anchor Community on?

Rust network protocol 2634 and build 167781 on Linux is the build Anchor Community runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Anchor Community, and is it online now?

Reading: offline. Anchor Community last answered 6 days 11 hours ago. Reading: 21% uptime over the last 7 full days. It was up 35 of 168 hours. Check: first contact. Rust Metrics logged it on 18 October 2026.

Rules and settings

What rules does Anchor Community enforce, and what are its settings?

No gather rate appears in the name: Anchor Community. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

What map is Anchor Community on?

Check: map. Procedural, size 2,000, seed 551438052, generated by the game on Anchor Community. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

How can you get onto Anchor Community?

Check: join. Open Rust, press F1, then enter client.connect 176.100.37.157: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 10 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.