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

FP1 Current Map

Offline 2.49.144.161:28015 checked 32d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,829top 72%
Last wipe32d 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
15k10k15k20k26 Sep27 Sep29 Sep30 Sep2 Oct3 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 peak1players, last three wipes

The first 48 hours of its last wipes

01234+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
Sat 26 Sep, 15:31 UTC32d 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 FP1 Current Map?

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

What wipe timing does FP1 Current Map follow?

To tell the rhythm of FP1 Current Map, 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. 32 days 3 hours ago the current world was made.

Tags

How should you read the tags on FP1 Current Map?

Tags published by FP1 Current Map, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs165948 (Build): Build 165948; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. 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 FP1 Current Map?

On Rust Metrics, FP1 Current Map sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does FP1 Current Map hold among Rust servers?

Player hours over seven days put FP1 Current Map at #16,829, in the top 72% of all ranked servers.

What player count does FP1 Current Map carry?

Status for FP1 Current Map: offline. Last seen 32 days 3 hours ago.

Server details

What location is FP1 Current Map hosted in?

No region comes from FP1 Current Map. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 2.49.144.161:28015.

What Rust version is FP1 Current Map on?

Version check: Rust network protocol 2634 and build 165948 on Windows, run by FP1 Current Map. To get in, your game needs the same protocol; Steam applies the update.

How reliable is FP1 Current Map, and is it online now?

Reading: offline. FP1 Current Map last answered 32 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 26 September 2026.

Settings and map

What rules does FP1 Current Map enforce, and what are its settings?

Reading the name gives no gather rate for FP1 Current Map. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on FP1 Current Map?

Procedural map on FP1 Current Map, made by the game's generator.

Connection

How do you connect to FP1 Current Map?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs165948,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs165948
Build Build 165948.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.