RUST METRICSFlight deck · live data
Data live Servers11,615 Players36,116 Populated2,895 Fresh wipes 3 h67 Scan5 min
‹ All servers117.20.69.122:28015
Offline Full Queue Fresh wipe Wipe due No query

My Rust Devblog 133 Server on Version 1051.72

Offline 117.20.69.122:28015 checked 19d ago

modded
COM 1 · connect

Server instruments

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

Players now

100% 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#14,332top 65%
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
15k10k15k20k10 Oct11 Oct13 Oct14 Oct16 Oct17 Oct

Top 65% 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 timing

What wipe timing does My Rust Devblog 133 Server on Version 1051.72 follow?

Its rhythm cannot be told from the wipes of My Rust Devblog 133 Server on Version 1051.72 on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC.

Lists and filters

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): Slots: 1; v1806 (Protocol): Your game must run protocol 1806 to get in; oxide (Oxide): It runs Oxide, also known as uMod; modded (Modded): Check: category. Modded, because plugins or settings alter the game; 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. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show My Rust Devblog 133 Server on Version 1051.72?

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.

Population

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: #14,332 on seven-day player hours, top 65% of all ranked servers.

How full does My Rust Devblog 133 Server on Version 1051.72 get?

Reading for My Rust Devblog 133 Server on Version 1051.72: offline at this moment; last seen 19 days 1 hours ago.

Server details

Which location does My Rust Devblog 133 Server on Version 1051.72 run from?

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. Connect using 117.20.69.122:28015.

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

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

Is My Rust Devblog 133 Server on Version 1051.72 up, and how often does it stay up?

Check: connection. My Rust Devblog 133 Server on Version 1051.72 is offline at this moment. Last contact was 19 days 1 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 10 October 2026.

Map and rules

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. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. VAC is off. That is Valve's anti-cheat.

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

The game generates a procedural map for My Rust Devblog 133 Server on Version 1051.72.

Join

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

To join: start Rust, press F1 and type client.connect 117.20.69.122:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as oxide,modded,mp1,v1806,h815a96ff

Game

mp1
Max players Slots: 1.
v1806
Protocol Your game must run protocol 1806 to get in.

Mods and access

oxide
Oxide It runs Oxide, also known as uMod.
modded
Modded Check: category. Modded, because plugins or settings alter the game.

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.