Rust Data

rustdata.spaceservers116.120.240.207:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 116.120.240.207:28015 checked 12h ago

NC Build Server Test

moddedoxide

Connect

srv = rust.server("116.120.240.207:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 2
rank #5,906 # top 27%
last wipe 6d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5219:0022:0012:0015:0018:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020019:0022:0012:0015:0018:0021:00

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 best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
12k4k6k8k19 Oct21 Oct23 Oct24 Oct26 Oct28 Oct

Top 27% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 36 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 21 Oct, 13:01 UTC6d ago 2 NaN 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.

display(srv.map, srv.info())

Map

5000 · seed 1758801068
Map of NC Build Server Test
map
Procedural Map
size
5000
seed
1758801068
Open on RustMaps

Server

srv.info()
address
116.120.240.207:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
21 Oct 2026, 15:43 UTC
hostname
–
first seen
19 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |EU · groups of 8+ · 112 on average90/999
1[NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |NA · groups of 8+ · 90 on average44/999
2[AU] Rusticated.com - Creative Sandbox | Build | Never WipesOC · groups of 8+ · 51 on average91/150
3Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFAEU · groups of 30+ · weekly · 35 on average93/250
4AQRUX RUST BUILD | CREATIVE | SANDBOXEU · groups of 8+ · monthly · 23 on average45/100
5KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfightgroups of 8+ · 23 on average28/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does NC Build Server Test rank?

Over the last seven days NC Build Server Test sits at #5,906 on player hours, in the top 27% of ranked servers.

What population does NC Build Server Test carry?

NC Build Server Test returns no live count at this refresh, having last been seen 12 hours ago. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 21:00 UTC, averaging 2 players.

Server data

What does performance look like on NC Build Server Test?

Averaged over 48 hours: 86 server fps, never under 66. Buildings, deployables and all else in the world took the count as high as 143,333 entities. Memory peaked at 3,429 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on NC Build Server Test?

The build is Rust network protocol 2635 and build 168909 on Windows, run by NC Build Server Test. Steam updates your game for you, but the protocol must match to join.

How reliable is NC Build Server Test, and is it up?

Offline now for NC Build Server Test, last seen 12 hours ago. A restart about 9 hours ago is what its reported uptime implies. 89 of 168 hours up over the last 7 full days, or 53%. Rust Data logged it first on 19 October 2026.

Which location does NC Build Server Test run from?

There is no region published for NC Build Server Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 116.120.240.207:28015 is its address.

Settings and map

Which rules apply on NC Build Server Test, and what settings?

The name NC Build Server Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has NC Build Server Test loaded?

Size 5,000, seed 1758801068: the procedural map on NC Build Server Test, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does NC Build Server Test wipe, and how often?

Too few wipes are on record for NC Build Server Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 6 days 18 hours ago.

On NC Build Server Test, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 36 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Which Rust Data filters and lists contain NC Build Server Test?

These Rust Data lists include NC Build Server Test: Modded Rust servers and Servers with build or creative tags. 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 week.

How should you read the server tags on NC Build Server Test?

The game's server browser reads these tags from NC Build Server Test: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

What is the way to join NC Build Server Test?

Enter client.connect 116.120.240.207:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players Slot count: 50.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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.

Rust Data 58,110 players 11,678 servers online