Rust Server Analytics 31,880 players11,622 servers
All servers
Drill-through Server detail

【南瓜】Build-Test

Online EA 45.125.45.246:28015 checked 10m ago

Drill-through
FilterServeris 【南瓜】Build-Test
Attributes
oxide
Last refreshed
Players now 12/ 101
7-day average 10 peak 28
Rank #953 top 4% · #89 in EA
Last wipe 6d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 12% full

Players

average and peak, with its wipes marked
AveragePeak
01020304006:0015:0000:0009:0019:0004:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020006:0015:0000:0009:0019:0004: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 4% of all ranked servers, top 16% in EA. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.5 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak24players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 22 OctMon 19 OctTue 13 Oct
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 24, 15 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 21:55 UTC6d ago 24 – running 1
Mon 19 Oct, 01:15 UTC10d ago 25 held half 3.9 days 4
Tue 13 Oct, 20:03 UTC15d ago 23 held half 5.2 days 0
Mon 12 Oct, 09:06 UTC16d ago 25 – 1.5 days 15
Sun 11 Oct, 17:55 UTC17d ago 25 – 0.6 days 2
Thu 8 Oct, 13:33 UTC20d ago 32 held half 3.2 days 0
Tue 6 Oct, 10:36 UTC22d ago 24 held half 2.1 days 12
Fri 2 Oct, 04:30 UTC27d ago 25 held half 4.3 days 0
Sun 27 Sep, 00:04 UTC32d ago 31 held half 5.2 days 5
Wed 23 Sep, 21:05 UTC35d ago 24 held half 3.1 days 3

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
ServerProfilePlayers now
Intoxicated SEA Sandbox - Creative | Build | Noclip EA · groups of 8+ · 10 on average 13 / 100
桃乐丝 UKN - 起床 | 死斗 | 训练 | 建筑 | 竞技场 EA · groups of 10+ · 10 on average 22 / 50
『夜猫子』PVE1000倍/快乐建家/NPC建筑/F1刷物品 EA · groups of 100+ · 2 on average 1 / 188
風紀委員 堤防部 EA · groups of 8+ · 1 on average 0 / 30
【开心萌橙PVE-kxmc】休闲娱乐/5倍/防抄家/任务 EA · groups of 20+ · monthly · 2 on average 2 / 150
可爱-1000倍PVE-不掉-突袭-养殖-僵尸-无限耐久 EA · groups of 8+ · biweekly · 1 on average 2 / 100

Quick answers

from the figures on this page

Wipe data

On what cycle does 【南瓜】Build-Test wipe?

No next wipe can be predicted for 【南瓜】Build-Test, which wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The current world dates from 6 days 3 hours.

On 【南瓜】Build-Test, what happens on wipe day?

Across recent wipes the busiest point averaged 24 players. Peak population for the latest wipe came 15 hours after it began. Above half that peak until the next wipe held in 100% of recent wipes.

Server

What is the hosting location of 【南瓜】Build-Test?

Its EA tag puts 【南瓜】Build-Test in Asia. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 45.125.45.246:28015.

What Rust build does 【南瓜】Build-Test run?

The platform is Windows, with Rust network protocol 2635 and build 168909 running on 【南瓜】Build-Test. Your game must match the protocol to join, and Steam applies that update.

Is 【南瓜】Build-Test up, and how steady is its uptime?

【南瓜】Build-Test reports online at the current check. About 6 days 1 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 99%, or 167 of 168 hours. It entered Rust Server Analytics records on 13 September 2026.

Is performance on 【南瓜】Build-Test stable?

The 48-hour average was 99 server fps; the low was 49. Buildings, deployables and all other world objects brought the entity total to 146,918. Memory use reached 6,217 MB at peak. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

Which meanings do the tags on 【南瓜】Build-Test carry?

The game's server browser reads the tags 【南瓜】Build-Test publishes: gmrust (Game mode): Survival in the standard Rust format; mp101 (Max players): Player slots: 101; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^k (Build server): Base design and building practice; ^o (Oxide): The Oxide (uMod) plugin framework is installed; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does 【南瓜】Build-Test appear across Rust Server Analytics's lists and filters?

These Rust Server Analytics lists include 【南瓜】Build-Test: Rust build and creative servers. On the server list, the filters that return it are: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Build server ^k and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Players now: At least 10.

Population

Against other Rust servers, how does 【南瓜】Build-Test compare?

Ranked on seven-day player hours, 【南瓜】Build-Test is #953 overall and #89 in Asia, within the top 4% of ranked servers.

At what level does 【南瓜】Build-Test run its population?

【南瓜】Build-Test holds 12 players of its 101 slots as of the latest update. Seven-day figures: an average of 10 players and a peak of 28. Averaged over 48 hours, activity is highest at 13:00 UTC with 25 players.

Settings

What settings and rules does 【南瓜】Build-Test use?

Gather rate is not mentioned in the name of 【南瓜】Build-Test. No custom group limit: 8 players is the standard. build & creative is the game mode, sandbox building, no gathering. Community is its listing; it is a community server. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, disabled.

What is the map for 【南瓜】Build-Test?

【南瓜】Build-Test uses a procedural map of size 4,000 with seed 1361858059, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

How to join

How do you connect to 【南瓜】Build-Test?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 45.125.45.246:28015.

Server tags

what each one means

Published as mp101,ptrak,$r?,v2635,^k,EA,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Survival in the standard Rust format.
mp101
Max players Player slots: 101.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol To join, your game version must match protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code The region code is blank.

Gameplay

^k
Build server Base design and building practice.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.

Region

EA
East Asia The server browser files it under East Asia.

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.