CarbonRustReactTest
Offline 185.51.127.189:28015 checked 34d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe 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
the same kind of game, then region, group limit, rate and wipes
- 17/ 100
- 291/ 400
- 199/ 225
- 124/ 100
- 396/ 1000
- 37/ 700
Quick answers
Tags and filters
Where does CarbonRustReactTest appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include CarbonRustReactTest: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on CarbonRustReactTest?
gmrust (Game mode): This is the standard Rust survival experience; mp50 (Max players): The slot count is 50; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs163794 (Build): The build number is 163794; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): Carbon is the plugin framework it uses — that is the tag list CarbonRustReactTest puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What location is CarbonRustReactTest in?
CarbonRustReactTest does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 185.51.127.189:28015.
How reliable is CarbonRustReactTest?
CarbonRustReactTest is down at the moment; it was last up 34 days 17 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 13 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for CarbonRustReactTest?
Rust network protocol 2633 and build 163794 is what CarbonRustReactTest runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does CarbonRustReactTest follow for wipes?
Too few wipes are on record for CarbonRustReactTest to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 39 days 10 hours.
Settings and map
Which rules and settings is CarbonRustReactTest running?
The name of CarbonRustReactTest contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Carbon. VAC is on: Valve's anti-cheat is active.
Which map is active on CarbonRustReactTest?
CarbonRustReactTest uses a game-generated procedural map.
Player count
Is CarbonRustReactTest busy?
CarbonRustReactTest was last seen 34 days 17 hours ago and is offline as you read this.
What's CarbonRustReactTest's rank among Rust servers?
For player hours in the last seven days, CarbonRustReactTest ranks #13,043, within the top – of ranked servers.
Join info
What's the way to join CarbonRustReactTest?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 185.51.127.189:28015.