BLD6384
NC Build Server Test
Offline 116.120.240.207:28015 checked 1d 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, measured since 19 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 29% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 36 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 13:01 UTC7d ago | 2 | – | running | 0 |
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.
-
01MODPlayers 235/999
-
02MODPlayers 157/999
-
03MODPlayers 31/150
-
04MODPlayers 45/100
-
05MODPlayers 21/100
-
06MODPlayers 38/100
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry NC Build Server Test?
These Rust Tracker lists carry NC Build Server Test: Modded servers, tracked live and Build, creative and sandbox servers. These filters surface it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on NC Build Server Test?
These tags are published by NC Build Server Test for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp50 (Max players): 50 slots on this server; ts8 (Group limit): Default team size: 8; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Times
What should you expect on NC Build Server Test when wipe day lands?
The average peak across recent wipes: 2 players. 36 hours after the latest wipe, the crowd peaked.
Which wipe times are confirmed for NC Build Server Test?
NC Build Server Test's rhythm cannot be told yet: too few wipes on record. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. Its world went live 7 days 6 hours.
Location and Status
Is NC Build Server Test up, and how does its uptime hold?
Tracking shows NC Build Server Test offline as of now, last seen 24 hours ago. The uptime it reports puts the last restart about 9 hours ago. Uptime stood at 53% for the last 7 full days, 89 of 168 hours online. First contact for Rust Tracker: 19 October 2026.
Which Rust build is NC Build Server Test running?
Confirmed for NC Build Server Test: Rust network protocol 2635 and build 168909, Windows. The same protocol is required to join, and Steam updates it for you.
What is performance like on NC Build Server Test?
Server fps held an average of 86 across the last 48 hours, never below 66. Maximum entities carried: 143,333, from buildings and deployables to everything else. Memory peaked at 3,429 MB. A climbing entity count and low fps are what register as lag for players.
Where does NC Build Server Test sit?
Region: none published by NC Build Server Test. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 116.120.240.207:28015.
Population
Is NC Build Server Test busy?
Last seen 24 hours ago; NC Build Server Test is offline at present. Seven-day average 0 players; peak 2. Busiest window in 48 hours: 12:00 UTC, 1 players on average.
Where does NC Build Server Test sit in the server rankings?
Seven-day player hours put NC Build Server Test at #6,384, within the top 29% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on NC Build Server Test?
Nothing in NC Build Server Test's name states a gather rate. Up to 8 players per group, the game's default. It runs survival, gather, build and raid: the standard game. Fighting and raiding between players are on. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Oxide. VAC is on, Valve's anti-cheat.
What map is NC Build Server Test on?
The map on NC Build Server Test is procedural, size 5,000, seed 1758801068, generated by the game. Size and seed match, so the map is the same: view it on RustMaps from this page.
How to Join
How do you get onto NC Build Server Test?
Open the console in Rust with F1 after starting the game, then type client.connect 116.120.240.207:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp50
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.