RUST METRICSFlight deck · live data
Data live Servers11,715 Players57,218 Populated3,311 Fresh wipes 3 h174 Scan5 min
‹ All servers176.58.193.118:28015
Offline Full Queue Fresh wipe Wipe due No query

Seeker test

Offline 176.58.193.118:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 1 /2

Players now

50% 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,579top 66%
Last wipe27d agono schedule published
Next wipe7d 8hThu 5 Nov, 19:00 UTC FW
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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 66% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 8hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 8hFW

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:06 UTC FW27d 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 Seeker test?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

How often does Seeker test wipe, and when?

With the force wipe, once a month, Seeker test wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 27 days 17 hours ago.

Tags

How should you read the tags on Seeker test?

These are the tags Seeker test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): Slots: 2; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Seeker test appear in Rust Metrics lists and filters?

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

Occupancy

Where does Seeker test sit in the rankings?

Ranking for Seeker test: #15,579 on seven-day player hours, top 66% of all ranked servers.

What is the population on Seeker test?

Seeker test is not responding; status offline, last seen 27 days 16 hours ago.

Operator and location

Where does Seeker test sit?

No region tag on Seeker test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.58.193.118:28015.

What Rust version is Seeker test on?

Rust network protocol 2633 and build 165217 on Windows is the build Seeker test runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Seeker test, and is it online?

Reading: offline. Seeker test last answered 27 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 1 October 2026.

Rules and settings

How is Seeker test configured, and what rules are in force?

No gather rate appears in the name: Seeker test. 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. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How do you connect to Seeker test?

Press F1 in Rust and enter client.connect 176.58.193.118: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 mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players Slots: 2.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.