RUST METRICSFlight deck · live data
Data live Servers11,738 Players62,312 Populated3,391 Fresh wipes 3 h192 Scan5 min
‹ All servers185.103.226.174:28015
Offline Full Queue Fresh wipe Wipe due No query

Staging Dev Server

Offline 185.103.226.174:28015 checked 42d ago

moddedcarbon
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,509no region published
Last wipe42d 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 Sep22 Sep23 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

Reset cycle

What wipe timing does Staging Dev Server follow?

To tell the rhythm of Staging Dev Server, 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. The world it runs now was made 42 days 16 hours ago.

Tag meanings

How should you read the tags on Staging Dev Server?

Tags published by Staging Dev Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164538 (Build): Build 164538; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Staging Dev Server appear in Rust Metrics lists and filters?

On Rust Metrics, Staging Dev Server sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

What position does Staging Dev Server hold among Rust servers?

Ranking for Staging Dev Server: #15,509 on seven-day player hours, top – of all ranked servers.

What player count does Staging Dev Server carry?

Reading for Staging Dev Server: offline at this moment; last seen 42 days 15 hours ago.

Server

Where does Staging Dev Server sit?

No region comes from Staging Dev Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 185.103.226.174:28015.

What Rust version is Staging Dev Server on?

Rust network protocol 2633 and build 164538 on Linux is the build Staging Dev Server runs. Matching protocol is required to join. Let Steam update your game.

How reliable is Staging Dev Server, and is it online now?

Check: connection. Staging Dev Server is offline at this moment. Last contact was 42 days 15 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 16 September 2026.

Map and rules

How is Staging Dev Server configured, and what rules are in force?

No gather rate appears in the name: Staging Dev Server. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. 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. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on Staging Dev Server?

The game generates a procedural map for Staging Dev Server.

Connection

How do you connect to Staging Dev Server?

Press F1 in Rust and enter client.connect 185.103.226.174: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 mp50,ptrak,$r?,v2633,gmrust,cs164538,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164538
Build Build 164538.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. Carbon.

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.