NC Build Server Test
Offline 116.120.240.207:28015 checked 1d ago
Server instruments
last reading Tue 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 66 · below 20 is lag, below 10 is badEntities
48 h range 137,394–143,045 · memory 2,874 MBUptime
9 h 40 min since its last restart, at the last readingPlayers
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- 162/999
- 186/999
- 42/150
- 22/100
- 8/100
- 22/100
Quick answers
from the figures on this pageWipe schedule
What happens on NC Build Server Test when wipe day comes?
At their busiest, its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 36 hours.
What wipe timing does NC Build Server Test follow?
Its rhythm cannot be told from the wipes of NC Build Server Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 7 days 7 hours ago the current world was made.
Lists and filters
Which tags does NC Build Server Test carry, and what do they mean?
These are the tags NC Build Server Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does NC Build Server Test appear in Rust Metrics lists and filters?
On Rust Metrics, NC Build Server Test sits in these lists: Modded Rust servers, checked live and Build and creative servers. These filters bring it up 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.
Player count
Where does NC Build Server Test sit in the rankings?
Ranking for NC Build Server Test: #6,383 on seven-day player hours, top 29% of all ranked servers.
What player count does NC Build Server Test carry?
Reading for NC Build Server Test: offline at this moment; last seen 25 hours ago. Check: players over seven days. Average 0, peak 2. Check: 48-hour peak. 12:00 UTC, 1 players on average.
Operator and location
Which location does NC Build Server Test run from?
Reading: location. NC Build Server Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 116.120.240.207:28015.
What Rust version is NC Build Server Test on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by NC Build Server Test. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for NC Build Server Test?
Reading: 79 server fps on average across the last 48 hours. It never dropped below 66. Peak entity count: 143,045. Buildings, deployables and all else included. Check: memory. Peak use was 3,429 MB. Lag, as players feel it, is low fps plus a climbing entity count.
How reliable is NC Build Server Test, and is it online now?
Reading: offline. NC Build Server Test last answered 25 hours ago. Check: restart. The uptime it reports puts the last restart about 9 hours ago. Reading: 53% uptime over the last 7 full days. It was up 89 of 168 hours. Check: first contact. Rust Metrics logged it on 19 October 2026.
Rules and settings
How is NC Build Server Test configured, and what rules are in force?
Check: gather rate. The name NC Build Server Test does not state one. 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. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
Which map is live on NC Build Server Test?
From seed 1758801068, the game generates the procedural map on NC Build Server Test. Its size is 5,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
How can you get onto NC Build Server Test?
To join: start Rust, press F1 and type client.connect 116.120.240.207:28015. Or press Launch Rust here and Steam opens the game and connects you.