RUST METRICSFlight deck · live data
Data live Servers11,757 Players71,901 Populated3,470 Fresh wipes 3 h213 Scan5 min
‹ All servers160.251.250.29:28015
Online Full Queue Fresh wipe Wipe due No query

RustServer_2626

Online 160.251.250.29:28015 checked 10m ago

COM 1 · connect

Server instruments

last reading Thu 21:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 136 SERVER FPS

Server fps

48 h low 104 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 46,205 ×1000

Entities

48 h range 44,301–46,707 · memory 2,027 MB
1239 ET SINCE RESTART 5D 23H

Uptime

5 days 23 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,290top 69%
Last wipe21d agono schedule published
Next wipe–too few wipes seen yet
Memory2,027MBat the last reading
REC 1

Players

AveragePeak
0123400:0009:0019:0003:0012:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020000:0009:0019:0003:0012:0021:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 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 peak3players, 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 3, 19 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 19:13 UTC21d ago 3 – 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 timing

What should you expect from wipe day on RustServer_2626?

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

When does RustServer_2626 wipe?

To tell the rhythm of RustServer_2626, 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 21 days 3 hours ago.

Tag meanings

Which tags does RustServer_2626 carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from RustServer_2626. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does RustServer_2626 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring RustServer_2626: 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 RustServer_2626 hold among Rust servers?

Player hours over seven days put RustServer_2626 at #15,290, in the top 69% of all ranked servers.

How full does RustServer_2626 get?

0 of 50 slots are filled on RustServer_2626 right now. Seven-day reading: 0 players on average.

Operator and location

What location is RustServer_2626 hosted in?

No region tag on RustServer_2626. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 160.251.250.29:28015.

What Rust version is RustServer_2626 on?

Reading: RustServer_2626, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does RustServer_2626 perform?

Reading: 133 server fps on average across the last 48 hours. It never dropped below 104. Peak entity count: 46,707. Buildings, deployables and all else included. Check: memory. Peak use was 2,378 MB. Lag, as players feel it, is low fps plus a climbing entity count.

How reliable is RustServer_2626, and is it online now?

Reading: online. RustServer_2626 answers right now. Reading: uptime. About 5 days 23 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does RustServer_2626 enforce, and what are its settings?

Reading the name gives no gather rate for RustServer_2626. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is RustServer_2626 on?

Check: map. Procedural, size 3,000, seed 2011, generated by the game on RustServer_2626. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto RustServer_2626?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
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.