Local Test Server [Carbon]
Offline 187.14.90.110: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
- 1001/ 100
- 63/ 400
- 44/ 245
- 128/ 100
- 80/ 1000
- 8/ 700
Quick answers
Tags and listings
Where does Local Test Server [Carbon] appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Local Test Server [Carbon] are: 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 Local Test Server [Carbon]?
Local Test Server [Carbon]'s game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): There are 10 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163493 (Build): The build number is 163493; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): Plugins are handled by Carbon. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What location is Local Test Server [Carbon] in?
Local Test Server [Carbon] does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 187.14.90.110:28015.
How reliable is Local Test Server [Carbon]?
Local Test Server [Carbon] is down at the moment; it was last up 34 days 13 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 13 September 2026.
What is the Rust version for Local Test Server [Carbon]?
On Windows, Local Test Server [Carbon] runs Rust network protocol 2633 and build 163493. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does Local Test Server [Carbon] follow for wipes?
Too few wipes are on record for Local Test Server [Carbon] to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 37 days 15 hours ago.
Rules and settings
What settings and rules have been applied to Local Test Server [Carbon]?
No gather rate appears in the name of Local Test Server [Carbon]. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. Carbon plugins are running here. VAC is off: Valve's anti-cheat is not active.
What's the map on Local Test Server [Carbon]?
The map on Local Test Server [Carbon] is procedural, made by the game.
Player count
Is Local Test Server [Carbon] busy?
The last sighting of Local Test Server [Carbon] was 34 days 13 hours ago; it is offline right now.
Join info
What's the process to join Local Test Server [Carbon]?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 187.14.90.110:28015.