RUST METRICSFlight deck · live data
Data live Servers11,823 Players72,372 Populated3,652 Fresh wipes 3 h214 Scan5 min
‹ All servers34.226.59.131:28015
Offline Full Queue Fresh wipe Wipe due No query

44s local dev test

Offline 34.226.59.131:28015 checked 23d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 0 /4

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,952top 71%
Last wipe23d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 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 timing

How often does 44s local dev test wipe, and when?

To tell the rhythm of 44s local dev test, 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 23 days 9 hours ago.

Tags

How should you read the tags on 44s local dev test?

Tags published by 44s local dev test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): Slots: 4; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Carbon handles the plugins here. 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 44s local dev test?

Rust Metrics lists featuring 44s local dev test: 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.

Population

What position does 44s local dev test hold among Rust servers?

Ranking for 44s local dev test: #15,952 on seven-day player hours, top 71% of all ranked servers.

What is the population on 44s local dev test?

Status for 44s local dev test: offline. Last seen 23 days 9 hours ago.

Server details

Which location does 44s local dev test run from?

Reading: location. 44s local dev test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 34.226.59.131:28015.

What Rust version is 44s local dev test on?

Version check: Rust network protocol 2634 and build 166652 on Linux, run by 44s local dev test. Matching protocol is required to join. Let Steam update your game.

How reliable is 44s local dev test, and is it online now?

44s local dev test reports offline. The last reading came 23 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 6 October 2026.

Rules and settings

What rules does 44s local dev test enforce, and what are its settings?

Reading the name gives no gather rate for 44s local dev test. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

What map is 44s local dev test on?

Check: map. Procedural, generated by the game, on 44s local dev test.

How to join

How can you get onto 44s local dev test?

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

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players Slots: 4.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Carbon handles the plugins here.

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.