RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers45.187.111.216:28015
Offline Full Queue Fresh wipe Wipe due No query

My Rust Devblog 133 Server on Version 1051.72

Offline 45.187.111.216:28015 checked 15d ago

modded
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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,426top 71%
Last wipe–no 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

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

When does My Rust Devblog 133 Server on Version 1051.72 wipe?

To tell the rhythm of My Rust Devblog 133 Server on Version 1051.72, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one.

Tags

How should you read the tags on My Rust Devblog 133 Server on Version 1051.72?

Check: tags. The game's server browser reads mp1 (Max players): The server holds 1 slots; v1806 (Protocol): Your game must run protocol 1806 to get in; oxide (Oxide): Check: framework. Oxide (uMod) handles plugins; modded (Modded): Plugins or settings make this a modded server; h815a96ff (Custom tag): Owner or plugin definition: this tag is not a standard Rust one from My Rust Devblog 133 Server on Version 1051.72. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does My Rust Devblog 133 Server on Version 1051.72 appear in Rust Metrics lists and filters?

On Rust Metrics, My Rust Devblog 133 Server on Version 1051.72 sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded.

Player count

What position does My Rust Devblog 133 Server on Version 1051.72 hold among Rust servers?

Ranking for My Rust Devblog 133 Server on Version 1051.72: #15,426 on seven-day player hours, top 71% of all ranked servers.

What player count does My Rust Devblog 133 Server on Version 1051.72 carry?

Status for My Rust Devblog 133 Server on Version 1051.72: offline. Last seen 15 days 18 hours ago.

Server

What location is My Rust Devblog 133 Server on Version 1051.72 hosted in?

No region tag on My Rust Devblog 133 Server on Version 1051.72. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 45.187.111.216:28015.

What Rust version is My Rust Devblog 133 Server on Version 1051.72 on?

Rust network protocol 1806 on Windows is the build My Rust Devblog 133 Server on Version 1051.72 runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on My Rust Devblog 133 Server on Version 1051.72, and is it online?

My Rust Devblog 133 Server on Version 1051.72 reports offline. The last reading came 15 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 October 2026.

Settings and map

What rules does My Rust Devblog 133 Server on Version 1051.72 enforce, and what are its settings?

No gather rate appears in the name: My Rust Devblog 133 Server on Version 1051.72. The group limit is not published. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. VAC is off. That is Valve's anti-cheat.

Which map is live on My Rust Devblog 133 Server on Version 1051.72?

Procedural map on My Rust Devblog 133 Server on Version 1051.72, made by the game's generator.

Join

How can you get onto My Rust Devblog 133 Server on Version 1051.72?

Press F1 in Rust and enter client.connect 45.187.111.216:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as oxide,modded,mp1,v1806,h815a96ff

Game

mp1
Max players The server holds 1 slots.
v1806
Protocol Your game must run protocol 1806 to get in.

Mods and access

oxide
Oxide Check: framework. Oxide (uMod) handles plugins.
modded
Modded Plugins or settings make this a modded server.

Other

h815a96ff
Custom tag Owner or plugin definition: this tag is not a standard Rust one.

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.