RUST METRICSFlight deck · live data
Data live Servers11,668 Players34,317 Populated2,844 Fresh wipes 3 h86 Scan5 min
‹ All servers92.61.103.60:28015
Offline Full Queue Fresh wipe Wipe due No query

nameserver

Offline 92.61.103.60:28015 checked 44d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 1 /3

Players now

33% 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,762no region published
Last wipe44d agono 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
15k10k15k20k20 Sep21 Sep
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 nameserver follow?

Its rhythm cannot be told from the wipes of nameserver on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 44 days 16 hours ago the current world was made.

Tags

How should you read the tags on nameserver?

Tags published by nameserver, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does nameserver appear in Rust Metrics lists and filters?

These Rust Metrics lists carry nameserver: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

What position does nameserver hold among Rust servers?

Player hours over seven days put nameserver at #14,762, in the top – of all ranked servers.

What player count does nameserver carry?

Status for nameserver: offline. Last seen 44 days 16 hours ago.

Operator and location

Which location does nameserver run from?

Reading: location. nameserver gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 92.61.103.60:28015.

What Rust version is nameserver on?

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

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

Check: connection. nameserver is offline at this moment. Last contact was 44 days 16 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 14 September 2026.

Map and rules

What settings and rules apply on nameserver?

No gather rate appears in the name: nameserver. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on nameserver?

The game generates a procedural map for nameserver.

How to join

How can you get onto nameserver?

Press F1 in Rust and enter client.connect 92.61.103.60: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 mp3,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players The server holds 3 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

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.