Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
No rank history yet.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Test_Dev_Server_Neruxnetzwerk based in?
No region is published for Test_Dev_Server_Neruxnetzwerk. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 138.201.226.233:28023.
Is Test_Dev_Server_Neruxnetzwerk up, and how steady is its uptime?
At this moment, Test_Dev_Server_Neruxnetzwerk is offline; the last time it was seen was 45 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
On what Rust version does Test_Dev_Server_Neruxnetzwerk sit?
You will find Test_Dev_Server_Neruxnetzwerk on Rust network protocol 2633 and build 162929, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does Test_Dev_Server_Neruxnetzwerk reset?
Test_Dev_Server_Neruxnetzwerk has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 54 days 7 hours.
Player count
Where does Test_Dev_Server_Neruxnetzwerk sit among Rust servers?
Over the last seven days, Test_Dev_Server_Neruxnetzwerk has #15,149 for player hours, in the top – of all ranked servers.
How many players does Test_Dev_Server_Neruxnetzwerk usually have?
It has been 45 days 5 hours since Test_Dev_Server_Neruxnetzwerk was last seen, and it is offline right now.
Tags and filters
What do Test_Dev_Server_Neruxnetzwerk's tags stand for?
The game's browser takes its cue from the tags Test_Dev_Server_Neruxnetzwerk has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs162929 (Build): Build number: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^y (Carbon): Plugin framework: Carbon. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Test_Dev_Server_Neruxnetzwerk?
These Rust Server Score lists count Test_Dev_Server_Neruxnetzwerk among them: Best community servers, graded. 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.
Server rules
What settings and rules apply on Test_Dev_Server_Neruxnetzwerk?
You will find no gather rate in the name of Test_Dev_Server_Neruxnetzwerk. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. Carbon plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Test_Dev_Server_Neruxnetzwerk uses?
Test_Dev_Server_Neruxnetzwerk runs a procedural map, which the game generates.
How to join
What is the way to join Test_Dev_Server_Neruxnetzwerk?
To connect, start Rust, press F1, and type client.connect 138.201.226.233:28023. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,gmrust,cs162929,ts8,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs162929
BuildBuild number: 162929.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^y
CarbonPlugin 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.
Not enough figures yet to write a report. Check back after a few days on the list.