RUST METRICSFlight deck · live data
Data live Servers11,875 Players97,136 Populated3,915 Fresh wipes 3 h398 Scan5 min
‹ All servers133.88.123.125:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_1985

Offline 133.88.123.125:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,948top 70%
Last wipe45d 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, 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 Sep24 Sep28 Sep1 Oct5 Oct9 Oct

Top 70% 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

Reset cycle

What wipe timing does RustServer_1985 follow?

Its rhythm cannot be told from the wipes of RustServer_1985 on record: there are too few. 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 45 days 21 hours ago.

Tag meanings

Which tags does RustServer_1985 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): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from RustServer_1985. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show RustServer_1985?

On Rust Metrics, RustServer_1985 sits in these lists: 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

Where does RustServer_1985 sit in the rankings?

Player hours over seven days put RustServer_1985 at #15,948, in the top 70% of all ranked servers.

How full does RustServer_1985 get?

Reading for RustServer_1985: offline at this moment; last seen 26 days 20 hours ago.

Operator and location

What location is RustServer_1985 hosted in?

No region tag on RustServer_1985. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 133.88.123.125:28015.

What Rust version is RustServer_1985 on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by RustServer_1985. To get in, your game needs the same protocol; Steam applies the update.

How reliable is RustServer_1985, and is it online now?

Reading: offline. RustServer_1985 last answered 26 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on RustServer_1985?

Check: gather rate. The name RustServer_1985 does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_1985 on?

Check: map. Procedural, size 3,000, seed 11236, generated by the game on RustServer_1985. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

What do you do to join RustServer_1985?

To join: start Rust, press F1 and type client.connect 133.88.123.125: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.