RUST METRICSFlight deck · live data
Data live Servers11,711 Players51,860 Populated3,326 Fresh wipes 3 h136 Scan5 min
‹ All servers37.20.237.54:28015
Offline Full Queue Fresh wipe Wipe due No query

UODA

Offline 37.20.237.54:28015 checked 24d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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,546top 68%
Last wipe24d 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
15k10k15k20k24 Sep27 Sep30 Sep4 Oct7 Oct10 Oct

Top 68% 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.

usual gap1 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 3 OctFri 2 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 07:54 UTC24d ago 1 – running 0
Fri 2 Oct, 07:59 UTC25d ago 1 – 1 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 happens on UODA when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does UODA follow?

To tell the rhythm of UODA, 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. 24 days 15 hours ago the current world was made.

Tag meanings

How should you read the tags on UODA?

Tags published by UODA, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): Slots: 500; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; 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.

Where does UODA appear in Rust Metrics lists and filters?

On Rust Metrics, UODA 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.

Occupancy

Where does UODA sit in the rankings?

Player hours over seven days put UODA at #15,546, in the top 68% of all ranked servers.

How full does UODA get?

UODA is not responding; status offline, last seen 24 days 14 hours ago.

Operator and location

Where does UODA sit?

No region comes from UODA. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 37.20.237.54:28015.

What Rust version is UODA on?

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

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

UODA reports offline. The last reading came 24 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 24 September 2026, recorded by Rust Metrics.

Settings and map

How is UODA configured, and what rules are in force?

Reading the name gives no gather rate for UODA. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on UODA?

The game generates a procedural map for UODA.

Connection

How can you get onto UODA?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players Slots: 500.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
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.