Open every day, at every hour Admission free 11,789 servers and 63,543 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

This server publishes no banner

Exhibit no. 6,381Acc. 2026.6381

NC Build Server Test

Rust server · in the archive since 19 October 2026

Offline 116.120.240.207:28015 checked 1d ago

moddedoxide
To visit
Players now 0/ 50
0% full
7-day average0peak 2
Rank#6,381top 29%
Last wipe7d agoWed 21 Oct, 15:43 UTC · no schedule published
Next wipe–too few wipes seen yet

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectedlast seen, 27 Oct 2026, 21:45 UTCAll times UTC.

The record of each wipe

  1. Wed 21 Oct 202613:01 UTC7d ago
    Peak
    2
    Crowd
    –
    Lasted
    running
    Players before
    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.

The rhythm

Wipe schedule

too few wipes seen yet

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

2wipe-day peakplayers, 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.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
00.250.50.75123:0012:0014:0017:0019:0021:00

Hourly average and peak, UTC.

Folder 2

Server performance

05010015020023:0012:0014:0017:0019: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.

Folder 3

Rank

RankRank in region
12k4k6k8k19 Oct21 Oct23 Oct24 Oct26 Oct28 Oct

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

Related exhibits

Similar servers

The same kind of game, then region, group limit, rate and wipes.

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags and filters

What do the server tags on NC Build Server Test mean?

These tags from NC Build Server Test, read by the game's server browser, are: gmrust (Game mode): This server runs standard Rust survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): Teams are capped at 8, the default the game ships; v2635 (Protocol): The server runs game protocol 2635; matching it is required to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), is installed here; ^z (Modded): Under Modded: the game is changed by plugins or settings. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.

Which Rust Server History lists and filters include NC Build Server Test?

These Rust Server History lists include NC Build Server Test: Modded Rust servers: the record and Rust build servers: the record. It appears under these filters 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.

Server entry

Does NC Build Server Test run smoothly?

Across the last 48 hours it averaged 83 server fps; the low was 66. Buildings, deployables and everything else in the world came to as many as 143,333 entities. Up to 3,429 MB of memory was used. Lag, as players feel it, has two sources: low fps and a rising entity count.

Which version of Rust does NC Build Server Test run?

Rust network protocol 2635 and build 168909 is the build NC Build Server Test runs, on Windows. The protocol must match to join, and Steam handles that update.

Is NC Build Server Test online, and how reliable is it?

Offline now, NC Build Server Test was last seen 24 hours ago. The uptime it reports puts the last restart at about 9 hours ago. 89 of 168 hours, or 53% of the time, over the last 7 full days. The first sighting by Rust Server History was on 19 October 2026.

Where is NC Build Server Test located?

You will find no region published by NC Build Server Test. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. You will find it at 116.120.240.207:28015.

Wipe history

What does wipe day look like on NC Build Server Test?

2 players on average was the busiest its recent wipes drew. 36 hours into the latest wipe the crowd peaked.

What is the wipe schedule on NC Build Server Test?

The rhythm of NC Build Server Test cannot be told yet, as too few of its wipes are on record. The monthly force wipe comes next on Thursday 5 November at 19:00 UTC, and every Rust server wipes then. 7 days 6 hours ago its current world was made.

Player counts

How does NC Build Server Test rank against other Rust servers?

Player hours over the last seven days put NC Build Server Test at #6,381: a place in the top 29% of all ranked servers.

How busy is NC Build Server Test?

NC Build Server Test is offline at present, having last been seen 24 hours ago. A seven-day average of 0 players is recorded, with a peak of 2. The busiest hour of the last 48 was 12:00 UTC, averaging 1 players.

Rules and settings

What are the rules and settings on NC Build Server Test?

You will not find a gather rate in the name of NC Build Server Test. The limit of 8 players per group is the game's default. survival is the game mode, the usual game, with gathering, building and raiding. PvP and raiding are enabled. Under Modded in the server browser, the game is changed by plugins or settings. The plugin count is Oxide. VAC from Valve is switched on.

Which map does NC Build Server Test run?

A procedural map of size 5,000 with seed 1758801068 is what NC Build Server Test runs, generated by the game. You can look at the map on RustMaps from this page, since one size and seed always give one map.

Join record

How do I join NC Build Server Test?

Press F1 in Rust to open the console, then enter client.connect 116.120.240.207:28015 to connect. Launch Rust from this page instead and you join through Steam with the connect already made.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode This server runs standard Rust survival.
mp50
Max players Slot count: 50.
ts8
Group limit Teams are capped at 8, the default the game ships.
v2635
Protocol The server runs game protocol 2635; matching it is required to join.
cs168909
Build This server runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard one.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is installed here.
^z
Modded Under Modded: the game is changed by plugins or settings.

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.