RUST METRICSFlight deck · live data
Data live Servers11,830 Players81,821 Populated3,745 Fresh wipes 3 h270 Scan5 min
‹ All servers80.123.69.14:28225
Offline Full Queue Fresh wipe Wipe due No query

outpost-bridge-test

Offline 80.123.69.14:28225 checked 22d ago

COM 1 · connect
Launch Rust and join

Server instruments

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

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#16,008top 72%
Last wipe22d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 72% 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
Tue 6 Oct, 18:36 UTC22d 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

Reset cycle

What should you expect from wipe day on outpost-bridge-test?

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

How often does outpost-bridge-test wipe, and when?

To tell the rhythm of outpost-bridge-test, too few of its wipes are on record. 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 22 days 20 hours ago.

Tags

How should you read the tags on outpost-bridge-test?

Tags published by outpost-bridge-test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does outpost-bridge-test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry outpost-bridge-test: 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.

Player count

What position does outpost-bridge-test hold among Rust servers?

Player hours over seven days put outpost-bridge-test at #16,008, in the top 72% of all ranked servers.

What is the population on outpost-bridge-test?

Reading for outpost-bridge-test: offline at this moment; last seen 22 days 19 hours ago.

Operator and location

What location is outpost-bridge-test hosted in?

Reading: location. outpost-bridge-test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 80.123.69.14:28225.

What Rust version is outpost-bridge-test on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by outpost-bridge-test. To get in, your game needs the same protocol; Steam applies the update.

Is outpost-bridge-test up, and how often does it stay up?

outpost-bridge-test reports offline. The last reading came 22 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 6 October 2026.

Map and rules

How is outpost-bridge-test configured, and what rules are in force?

Check: gather rate. The name outpost-bridge-test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. 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 outpost-bridge-test?

Procedural map on outpost-bridge-test, made by the game's generator.

How to join

How can you get onto outpost-bridge-test?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players The server holds 2 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.