RUST METRICSFlight deck · live data
Data live Servers11,662 Players33,506 Populated2,814 Fresh wipes 3 h80 Scan5 min
‹ All servers138.201.226.233:28023
Offline Full Queue Fresh wipe Wipe due No query

Test_Dev_Server_Neruxnetzwerk

Offline 138.201.226.233:28023 checked 45d ago

carbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,149no region published
Last wipe54d 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
No rank history yet.
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 Test_Dev_Server_Neruxnetzwerk wipe, and when?

The rhythm of Test_Dev_Server_Neruxnetzwerk's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 54 days 12 hours ago.

Tags

How should you read the tags on Test_Dev_Server_Neruxnetzwerk?

These are the tags Test_Dev_Server_Neruxnetzwerk publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): Build 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^y (Carbon): Carbon handles the plugins here. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Test_Dev_Server_Neruxnetzwerk?

Rust Metrics lists featuring Test_Dev_Server_Neruxnetzwerk: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Carbon ^y; Group limit: 5 or more.

Occupancy

What position does Test_Dev_Server_Neruxnetzwerk hold among Rust servers?

Player hours over seven days put Test_Dev_Server_Neruxnetzwerk at #15,149, in the top – of all ranked servers.

What is the population on Test_Dev_Server_Neruxnetzwerk?

Test_Dev_Server_Neruxnetzwerk is not responding; status offline, last seen 45 days 9 hours ago.

Server

Where does Test_Dev_Server_Neruxnetzwerk sit?

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

What Rust version is Test_Dev_Server_Neruxnetzwerk on?

Rust network protocol 2633 and build 162929 on Linux is the build Test_Dev_Server_Neruxnetzwerk runs. To get in, your game needs the same protocol; Steam applies the update.

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

Reading: offline. Test_Dev_Server_Neruxnetzwerk last answered 45 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on Test_Dev_Server_Neruxnetzwerk?

No gather rate appears in the name: Test_Dev_Server_Neruxnetzwerk. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test_Dev_Server_Neruxnetzwerk?

The game generates a procedural map for Test_Dev_Server_Neruxnetzwerk.

Connection

How can you get onto Test_Dev_Server_Neruxnetzwerk?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs162929,ts8,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players 100 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs162929
Build Build 162929.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^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.