RUST METRICSFlight deck · live data
Data live Servers11,604 Players34,824 Populated2,902 Fresh wipes 3 h67 Scan5 min
‹ All servers121.79.211.86:28015
Offline Full Queue Fresh wipe Wipe due No query

AmpersandMan

Offline 121.79.211.86:28015 checked 19d 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,697top 62%
Last wipe19d 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 06:26 UTC19d 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 happens on AmpersandMan when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does AmpersandMan wipe?

Its rhythm cannot be told from the wipes of AmpersandMan on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 19 days 23 hours ago.

Lists and filters

Which tags does AmpersandMan carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): Game build reading: 167058; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from AmpersandMan. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does AmpersandMan appear in Rust Metrics lists and filters?

On Rust Metrics, AmpersandMan sits in these lists: 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.

Occupancy

What position does AmpersandMan hold among Rust servers?

Ranking for AmpersandMan: #13,697 on seven-day player hours, top 62% of all ranked servers.

What is the population on AmpersandMan?

AmpersandMan is not responding; status offline, last seen 19 days 21 hours ago.

Server

Where does AmpersandMan sit?

Reading: location. AmpersandMan gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 121.79.211.86:28015.

What Rust version is AmpersandMan on?

Reading: AmpersandMan, Rust network protocol 2634 and build 167058, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

AmpersandMan reports offline. The last reading came 19 days 21 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 8 October 2026.

Settings and map

What rules does AmpersandMan enforce, and what are its settings?

No gather rate appears in the name: AmpersandMan. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is AmpersandMan on?

Check: map. Procedural, generated by the game, on AmpersandMan.

How to join

How do you connect to AmpersandMan?

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build Game build reading: 167058.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.