RUST METRICSFlight deck · live data
Data live Servers11,628 Players32,585 Populated2,817 Fresh wipes 3 h70 Scan5 min
‹ All servers92.208.174.128:28015
Offline Full Queue Fresh wipe Wipe due No query

neurocore solo: experimental

Offline 92.208.174.128:28015 checked 3d ago

moddedcarbon
COM 1 · connect

Server instruments

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

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,341top 69%
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
15k10k15k20k5 Oct9 Oct13 Oct17 Oct25 Oct29 Oct

Top 69% 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

Reset cycle

What wipe timing does neurocore solo: experimental follow?

Its rhythm cannot be told from the wipes of neurocore solo: experimental on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 23 days 7 hours ago.

Tags

How should you read the tags on neurocore solo: experimental?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Check: framework. Carbon from neurocore solo: experimental. 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 neurocore solo: experimental?

On Rust Metrics, neurocore solo: experimental sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does neurocore solo: experimental sit in the rankings?

Ranking for neurocore solo: experimental: #15,341 on seven-day player hours, top 69% of all ranked servers.

How full does neurocore solo: experimental get?

Status for neurocore solo: experimental: offline. Last seen 3 days 11 hours ago. Seven-day reading: 0 players on average.

Server details

Which location does neurocore solo: experimental run from?

No region tag on neurocore solo: experimental. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 92.208.174.128:28015.

What Rust version is neurocore solo: experimental on?

Rust network protocol 2635 and build 168909 on Linux is the build neurocore solo: experimental runs. Matching protocol is required to join. Let Steam update your game.

How reliable is neurocore solo: experimental, and is it online now?

neurocore solo: experimental reports offline. The last reading came 3 days 11 hours ago. Uptime for the last 7 full days: 6 of 168 hours, or 4%. Check: first contact. Rust Metrics logged it on 5 October 2026.

Settings and map

How is neurocore solo: experimental configured, and what rules are in force?

Reading the name gives no gather rate for neurocore solo: experimental. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. VAC is off. That is Valve's anti-cheat.

What map is neurocore solo: experimental on?

The game generates a procedural map for neurocore solo: experimental.

How to join

How do you connect to neurocore solo: experimental?

Check: join. Open Rust, press F1, then enter client.connect 92.208.174.128:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players The server holds 3 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^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.