RUST METRICSFlight deck · live data
Data live Servers11,893 Players98,350 Populated3,934 Fresh wipes 3 h402 Scan5 min
‹ All servers38.34.123.200:28015
Offline Full Queue Fresh wipe Wipe due No query

fp-h1-test

Offline 38.34.123.200:28015 checked 9d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,338top 69%
Last wipe9d agono schedule published
Next wipe–no wipe 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
15k10k15k20k19 Oct21 Oct22 Oct24 Oct25 Oct27 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does fp-h1-test follow?

To tell the rhythm of fp-h1-test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 9 days 22 hours ago.

Tags

Which tags does fp-h1-test carry, and what do they mean?

These are the tags fp-h1-test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show fp-h1-test?

Rust Metrics lists featuring fp-h1-test: 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

What position does fp-h1-test hold among Rust servers?

Player hours over seven days put fp-h1-test at #15,338, in the top 69% of all ranked servers.

How full does fp-h1-test get?

fp-h1-test is not responding; status offline, last seen 9 days 15 hours ago.

Server

Which location does fp-h1-test run from?

Reading: location. fp-h1-test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 38.34.123.200:28015.

What Rust version is fp-h1-test on?

Rust network protocol 2634 and build 167781 on Linux is the build fp-h1-test runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on fp-h1-test, and is it online?

Check: connection. fp-h1-test is offline at this moment. Last contact was 9 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 October 2026.

Map and rules

What rules does fp-h1-test enforce, and what are its settings?

Check: gather rate. The name fp-h1-test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is fp-h1-test on?

Check: map. Procedural, generated by the game, on fp-h1-test.

Join

How do you connect to fp-h1-test?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players 5 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.