RUST METRICSFlight deck · live data
Data live Servers11,809 Players80,805 Populated3,802 Fresh wipes 3 h104 Scan5 min
‹ All servers178.168.48.156:28015
Offline Full Queue Fresh wipe Wipe due No query

Snipe

Offline 178.168.48.156:28015 checked 11d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 1 /15

Players now

7% 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#12,982top 60%
Last wipe13d 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
15k10k15k20k13 Oct15 Oct17 Oct20 Oct22 Oct24 Oct

Top 60% 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.

usual gap2.3 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 15 OctTue 13 Oct
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 15 Oct, 16:12 UTC13d ago 1 – running 0
Tue 13 Oct, 08:25 UTC15d ago 1 held half 2.3 days 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 Snipe when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does Snipe wipe?

The rhythm of Snipe's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 13 days 4 hours ago the current world was made.

Tags

How should you read the tags on Snipe?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Game build reading: 167584; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Snipe. 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 Snipe?

These Rust Metrics lists carry Snipe: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

Where does Snipe sit in the rankings?

Player hours over seven days put Snipe at #12,982, in the top 60% of all ranked servers.

How full does Snipe get?

Reading for Snipe: offline at this moment; last seen 11 days 7 hours ago.

Server

Where does Snipe sit?

No region comes from Snipe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 178.168.48.156:28015.

What Rust version is Snipe on?

Rust network protocol 2634 and build 167584 on Windows is the build Snipe runs. Matching protocol is required to join. Let Steam update your game.

Is Snipe up, and how often does it stay up?

Reading: offline. Snipe last answered 11 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 October 2026, recorded by Rust Metrics.

Map and rules

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

No gather rate appears in the name: Snipe. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Snipe?

Procedural map on Snipe, made by the game's generator.

Connection

How do you connect to Snipe?

To join: start Rust, press F1 and type client.connect 178.168.48.156:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players The server holds 15 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build Game build reading: 167584.
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.