Rust Server TrendsSeismic network · station log
Recording Stations11,726 Players49,195 Active3,240 Wipes · 3 h114 48 h

Station XX-6387 · no signal

NC Build Server Test

Offline 116.120.240.207:28015 checked 1d ago

moddedoxide
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0falling
−1 players on the day
7-day average
0
peak 2
Rank
#6,387
top 29%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-6387 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0falling−1 players
Sharpest hour
−1into Tue 14:00 UTC
Peak · 48 h
1most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.250.50.75111:0013:0015:0017:0019:0021:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

025507510011:0013:0015: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.

Channel 3 · rank movement

Rank

daily · 1 is best
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.

Expected events

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.

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 21 Oct, 13:01 UTC7d ago M0.3rising 2 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
159/ 999
190/ 999
46/ 150
Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA EU · groups of 30+ · weekly · 37 on average
22/ 100
AQRUX RUST BUILD | CREATIVE | SANDBOX EU · groups of 8+ · monthly · 24 on average
3/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on NC Build Server Test?

NC Build Server Test runs a procedural map of size 5,000 with seed 1758801068, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on NC Build Server Test?

The name of NC Build Server Test gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Live population

How many players are recorded on NC Build Server Test right now?

A reading taken now finds NC Build Server Test offline; the most recent activity was 26 hours ago. The seven-day average is 0 players, with a peak of 2. The last 48 hours show their highest activity at 12:00 UTC, averaging 1 players.

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

Over the last seven days, NC Build Server Test recorded enough player hours to reach #6,387 worldwide, placing it in the top 29% of all ranked servers.

Server details

How reliably does NC Build Server Test stay online?

NC Build Server Test is down at the moment; the last recorded contact was 26 hours ago. Its reported uptime points to a restart about 9 hours ago. 65 of 168 hours in the last 7 full days were up time, 39% of the total. Its earliest appearance in the records of Rust Server Trends dates to 19 October 2026.

How well does NC Build Server Test perform under load?

Its average server fps over the last 48 hours was 79, and it never dropped below 66. At its highest, it carried 143,045 entities: buildings, deployables and the world's other contents. It reached a ceiling of 3,429 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does NC Build Server Test run from?

No region is published by NC Build Server Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 116.120.240.207:28015 is the address it uses.

What build of Rust does NC Build Server Test use?

On Windows, NC Build Server Test runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

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

On average, the busiest point of its recent wipes drew 2 players. 36 hours into the latest wipe, the crowd reached its peak.

On what timetable does NC Build Server Test run its wipes?

The rhythm of NC Build Server Test cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 7 days 8 hours.

Server tags

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

Tags published by NC Build Server Test and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does NC Build Server Test appear?

These Rust Server Trends lists include NC Build Server Test: Modded Rust servers, tracked live and Rust build and creative servers, live. 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.

How to join

How do you connect to NC Build Server Test?

You can connect by pressing F1 in Rust and typing client.connect 116.120.240.207:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.