RUST METRICSFlight deck · live data
Data live Servers11,842 Players74,292 Populated3,699 Fresh wipes 3 h224 Scan5 min
‹ All servers51.79.46.140:25093
Online Full Queue Fresh wipe Wipe due No query

n28766149

Online 51.79.46.140:25093 checked 10m ago

COM 1 · connect

Server instruments

last reading Thu 12:00 UTC
0 19 38 56 75 PAX 0 /75

Players now

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

Server fps

48 h low 233 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 8,065 ×1000

Entities

48 h range 6,013–8,303 · memory 3,125 MB
1239 ET SINCE RESTART 3D 01H

Uptime

3 days 1 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,326top 69%
Last wipe22d agono schedule published
Next wipe–no wipe seen yet
Memory3,125MBat the last reading
REC 1

Players

AveragePeak
0123414:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040014:0023:0008:0017:0003:0012: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 6 Oct. 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 Oct11 Oct15 Oct20 Oct24 Oct29 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 n28766149 follow?

To tell the rhythm of n28766149, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 22 days 18 hours ago.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp75 (Max players): 75 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from n28766149. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does n28766149 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring n28766149: 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.

Player count

What position does n28766149 hold among Rust servers?

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

What is the population on n28766149?

Current headcount on n28766149: 0 players, 75 slots available. Check: player average. 0 over the last seven days.

Operator and location

Where does n28766149 sit?

No region comes from n28766149. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 51.79.46.140:25093.

What Rust version is n28766149 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by n28766149. Check: protocol. To join, your game must match; Steam handles the update.

How does n28766149 perform?

Over the last 48 hours the average was 239 server fps; the floor was 233. Check: entities. The peak was 8,303, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,245 MB. Expect lag when fps falls and entities climb.

How reliable is n28766149, and is it online now?

Check: connection. n28766149 is online at this moment. By its reported uptime, the last restart was roughly 3 days 1 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 6 October 2026.

Rules and settings

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

Check: gather rate. The name n28766149 does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on n28766149?

Size 1,500 and seed 50000: the game generates the procedural map on n28766149 from them. View it on RustMaps from this page: matching size and seed give an identical map.

Join

What do you do to join n28766149?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp75
Max players 75 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
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.