RUST METRICSFlight deck · live data
Data live Servers11,610 Players40,842 Populated2,876 Fresh wipes 3 h140 Scan5 min
‹ All servers193.248.137.50:28015
Offline Full Queue Fresh wipe Wipe due No query

SERVER2

Offline 193.248.137.50:28015 checked 9d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#13,060top 59%
Last wipe19d agono schedule published
Next wipe–no rhythm it keeps
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 Sep2 Oct8 Oct15 Oct21 Oct27 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 10 OctFri 9 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 29 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 08:30 UTC19d ago 1 – running 0
Fri 9 Oct, 15:06 UTC20d ago 1 – 0.7 days 0
Fri 2 Oct, 21:15 UTC27d ago 0 – 6.7 days 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 SERVER2?

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

What wipe timing does SERVER2 follow?

There is no next wipe to predict: SERVER2 wipes at irregular times. 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 19 days 17 hours ago.

Tag meanings

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

Tags published by SERVER2, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show SERVER2?

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

Where does SERVER2 sit in the rankings?

Ranking for SERVER2: #13,060 on seven-day player hours, top 59% of all ranked servers.

How full does SERVER2 get?

Reading for SERVER2: offline at this moment; last seen 9 days 17 hours ago.

Server details

Where does SERVER2 sit?

No region tag on SERVER2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 193.248.137.50:28015.

What Rust version is SERVER2 on?

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

How reliable is SERVER2, and is it online now?

Check: connection. SERVER2 is offline at this moment. Last contact was 9 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 26 September 2026, recorded by Rust Metrics.

Settings and map

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

Check: gather rate. The name SERVER2 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: 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. Anti-cheat reading: VAC on, Valve's system.

Which map is live on SERVER2?

The game generates a procedural map for SERVER2.

Connection

What do you do to join SERVER2?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.