RUST METRICSFlight deck · live data
Data live Servers11,726 Players56,761 Populated3,425 Fresh wipes 3 h136 Scan5 min
‹ All servers37.78.41.127:28015
Offline Full Queue Fresh wipe Wipe due No query

mon1x14

Offline 37.78.41.127:28015 checked 18d 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,842top 72%
Last wipe18d 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 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

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 13:42 UTC18d 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

Wipe schedule

What should you expect from wipe day on mon1x14?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 4 hours in.

How often does mon1x14 wipe, and when?

Its rhythm cannot be told from the wipes of mon1x14 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. 18 days 9 hours ago the current world was made.

Tag meanings

How should you read the tags on mon1x14?

These are the tags mon1x14 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): The server runs game build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 mon1x14?

These Rust Metrics lists carry mon1x14: 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.

Player count

Where does mon1x14 sit in the rankings?

Player hours over seven days put mon1x14 at #15,842, in the top 72% of all ranked servers.

What player count does mon1x14 carry?

mon1x14 is not responding; status offline, last seen 18 days ago.

Server

Where does mon1x14 sit?

No region tag on mon1x14. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 37.78.41.127:28015.

What Rust version is mon1x14 on?

Rust network protocol 2634 and build 167398 on Windows is the build mon1x14 runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on mon1x14, and is it online?

Reading: offline. mon1x14 last answered 18 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 9 October 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: mon1x14. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on mon1x14?

Check: map. Procedural, generated by the game, on mon1x14.

How to join

How can you get onto mon1x14?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build The server runs game build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.