Statistical profileOnline
NC Build Server Test
116.120.240.207:28015 checked 6m ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak 2
Rank
#6,377
top 29%
Last wipe
7d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- There were 0 players on it, 0% of its 50 slots.
- Over the last seven days it averaged 0 players, with a peak of 2.
- It ranks #6,377 of all ranked servers, the top 29%, on player hours over the last seven days.
- Its current map went up 7d ago.
2. Players
Figure 1: Players on NC Build Server Test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 29% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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
2
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 2, 36 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 13:01 UTC7d ago | 2 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of NC Build Server Test
5000 · seed 1758801068
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 5000 |
| Seed | 1758801068 |
8. Server characteristics
Table 3: Characteristics of NC Build Server Test
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| [EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | EU · groups of 8+ · 116 on average | 65 / 999 |
| [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 90 on average | 158 / 999 |
| [AU] Rusticated.com - Creative Sandbox | Build | Never Wipes | OC · groups of 8+ · 52 on average | 74 / 150 |
| Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA | EU · groups of 30+ · weekly · 37 on average | 10 / 100 |
| AQRUX RUST BUILD | CREATIVE | SANDBOX | EU · groups of 8+ · monthly · 24 on average | 1 / 100 |
| KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfight | groups of 8+ · 23 on average | 19 / 100 |
10. Quick answers
From the figures on this page.
Wipe details
On what schedule are wipes carried out on NC Build Server Test?
The rhythm of NC Build Server Test's wipes cannot yet be told: too few are on record. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. The present world dates from 7 days 11 hours.
How is wipe day run on NC Build Server Test?
An average of 2 players attended at peak across recent wipes. The peak of the latest wipe's crowd came 36 hours after it began.
Server details
Is NC Build Server Test up, and how well has it held up?
NC Build Server Test is online at the time of this release. By its own reported uptime, it restarted about 9 hours ago. Of the 168 hours in the last 7 full days, it was up 65 of them, or 39%. First recorded by Rust Census on 19 October 2026.
How well does NC Build Server Test perform?
Average server fps over the last 48 hours was 79, with a low of 66. The world carried up to 143,045 entities, including buildings, deployables and all else. The peak memory use recorded was 3,429 MB. Lag, as players feel it, comes from low fps and a climbing entity count.
Which location does NC Build Server Test run from?
No region is given by NC Build Server Test. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. At 116.120.240.207:28015 it is addressed.
What version of Rust has been recorded on NC Build Server Test?
This release lists NC Build Server Test on Rust network protocol 2635 and build 168909, running on Windows. To join, your game has to be on the same protocol; Steam handles the update.
Player counts
How many players does NC Build Server Test carry?
At counting time NC Build Server Test recorded 0 players across 50 slots. Averaged over seven days: 0 players, with a peak of 2. An average of 1 players was recorded at 12:00 UTC, the busiest hour of the last 48.
In the rankings of Rust servers, where is NC Build Server Test placed?
For seven-day player hours, NC Build Server Test is ranked #6,377, placing it in the top 29% of all ranked servers.
Lists and tags
On Rust Census, which lists and filters carry NC Build Server Test?
The Rust Census lists that NC Build Server Test fits are: Modded Rust servers, counted and Rust build servers: listed. Under these filters it comes 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.
The tags on NC Build Server Test: what do they indicate?
Read by the game's server browser, NC Build Server Test publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Map and rules
What map is listed for NC Build Server Test?
Size 5,000 and seed 1758801068: that is the procedural map on NC Build Server Test, generated by the game. The same size and seed produce the same map; RustMaps shows it from this page.
What settings and rules have been listed for NC Build Server Test?
No gather rate is given in the name of NC Build Server Test. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. Modded is its section in the server browser, because plugins or settings change the game. Plugins on it number Oxide. The server runs VAC, Valve's anti-cheat.
Connecting
How can you connect to NC Build Server Test?
Enter client.connect 116.120.240.207:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp50 | Max players 50 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Game build: 168909. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded 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.