RUST METRICSFlight deck · live data
Data live Servers11,826 Players82,123 Populated3,756 Fresh wipes 3 h273 Scan5 min
‹ All servers128.65.59.21:29115
Offline Full Queue Fresh wipe Wipe due No query

probe

Offline 128.65.59.21:29115 checked 6d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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,335top 69%
Last wipe6d 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
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 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 peak0players, last three wipes

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 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 14:39 UTC7d ago 0 – 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 probe?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does probe wipe?

Its rhythm cannot be told from the wipes of probe 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 in play was created 6 days 23 hours ago.

Lists and filters

How should you read the tags on probe?

These are the tags probe publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): Game build reading: 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does probe appear in Rust Metrics lists and filters?

These Rust Metrics lists carry probe: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

What position does probe hold among Rust servers?

Ranking for probe: #15,335 on seven-day player hours, top 69% of all ranked servers.

What player count does probe carry?

Reading for probe: offline at this moment; last seen 6 days 23 hours ago. Check: player average. 0 over the last seven days.

Operator and location

What location is probe hosted in?

Reading: location. probe gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 128.65.59.21:29115.

What Rust version is probe on?

Rust network protocol 2634 and build 166494 on Windows is the build probe runs. Check: protocol. To join, your game must match; Steam handles the update.

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

probe reports offline. The last reading came 6 days 23 hours ago. Uptime for the last 6 full days: 0 of 144 hours, or 0%. The first sighting on Rust Metrics was 22 October 2026.

Rules and settings

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

Check: gather rate. The name probe does not state one. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

What map is probe on?

The game generates a procedural map for probe.

How to join

What do you do to join probe?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players Slots: 500.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build Game build reading: 166494.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: Carbon.

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.