Skip to the page
Network live 11,809 servers online 80,805 players aboard 104 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

【南瓜】Build-Test

Online EA 45.125.45.246:28015 checked 8m ago

oxide
Tracking number · connect
Wipe progress · wiped 5d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
6/ 101 players now 6% full
107-day averagepeak 28
#955ranktop 4% · #89 in EA
5d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
01020304021:0006:0015:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

05010015020021:0006:0015:0023:0008:0017: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 Sep5 Oct13 Oct20 Oct28 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.

3.5 daysusual gapbetween real wipes
25%on rhythmof its recent wipes
24wipe-day peakplayers, last three wipes
100%crowd heldof 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

every wipe as a delivery, newest first
  1. Thu 22 Oct, 21:55 UTC 22:55 UK · 5d ago
    Wipe delivered
    Peak
    24
    Crowd
    –
    Lasted
    running
    Players before
    1
  2. Mon 19 Oct, 01:15 UTC 02:15 UK · 9d ago
    Wipe delivered
    Peak
    25
    Crowd
    held half
    Lasted
    3.9 days
    Players before
    4
  3. Tue 13 Oct, 20:03 UTC 21:03 UK · 15d ago
    Wipe delivered
    Peak
    23
    Crowd
    held half
    Lasted
    5.2 days
    Players before
    0
  4. Mon 12 Oct, 09:06 UTC 10:06 UK · 16d ago
    Wipe delivered
    Peak
    25
    Crowd
    –
    Lasted
    1.5 days
    Players before
    15
  5. Sun 11 Oct, 17:55 UTC 18:55 UK · 17d ago
    Wipe delivered
    Peak
    25
    Crowd
    –
    Lasted
    0.6 days
    Players before
    2
  6. Thu 8 Oct, 13:33 UTC 14:33 UK · 20d ago
    Wipe delivered
    Peak
    32
    Crowd
    held half
    Lasted
    3.2 days
    Players before
    0
  7. Tue 6 Oct, 10:36 UTC 11:36 UK · 22d ago
    Wipe delivered
    Peak
    24
    Crowd
    held half
    Lasted
    2.1 days
    Players before
    12
  8. Fri 2 Oct, 04:30 UTC 05:30 UK · 26d ago
    Wipe delivered
    Peak
    25
    Crowd
    held half
    Lasted
    4.3 days
    Players before
    0
  9. Sun 27 Sep, 00:04 UTC 01:04 UK · 31d ago
    Wipe delivered
    Peak
    31
    Crowd
    held half
    Lasted
    5.2 days
    Players before
    5
  10. Wed 23 Sep, 21:05 UTC 22:05 UK · 34d ago
    Wipe delivered
    Peak
    24
    Crowd
    held half
    Lasted
    3.1 days
    Players before
    3
Show all 14 wipes
  1. Mon 21 Sep, 22:30 UTC 23:30 UK · 36d ago
    Wipe delivered
    Peak
    33
    Crowd
    –
    Lasted
    1.9 days
    Players before
    0
  2. Mon 21 Sep, 12:18 UTC 13:18 UK · 37d ago
    Wipe delivered
    Peak
    30
    Crowd
    –
    Lasted
    0.4 days
    Players before
    24
  3. Thu 17 Sep, 23:45 UTC 00:45 UK · 40d ago
    Wipe delivered
    Peak
    27
    Crowd
    held half
    Lasted
    3.5 days
    Players before
    3
  4. Sun 13 Sep, 16:19 UTC 17:19 UK · 45d ago
    Wipe delivered
    Peak
    33
    Crowd
    held half
    Lasted
    4.3 days
    Players before
    16

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 parcels

Similar servers

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

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

Quick answers

From the figures on this page.

Population

How does 【南瓜】Build-Test compare with other Rust servers in the rankings?

Ranked #955 on player hours over the last seven days, 【南瓜】Build-Test is #89 in Asia and in the top 4% of all ranked servers.

What is the current population on 【南瓜】Build-Test?

At the moment 6 players are on 【南瓜】Build-Test, which has 101 slots. The seven-day figures show an average of 10 players and a peak of 28. The busiest hour over the last 48 hours was 13:00 UTC, averaging 25 players.

Server rules

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

Size 4,000 and seed 1361858059 define the procedural map 【南瓜】Build-Test runs, generated by the game. You can see the map on RustMaps from this page, since one size and seed give one map.

What settings and rules should you know for 【南瓜】Build-Test?

The name of 【南瓜】Build-Test gives no gather rate. The game's default applies: 8 players to a group at most. You get build & creative here, no gathering, just sandbox building. It appears in the server browser under Community, being a community server. Plugins come from Oxide. The VAC anti-cheat from Valve is disabled.

Server details

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

With its EA tag, 【南瓜】Build-Test places itself in Asia. The location shown on Rust Wipe Tracker is the one a server gives; where the machine stands is not looked up. You will find it at 45.125.45.246:28015.

Does 【南瓜】Build-Test perform well?

The 48-hour average for server fps stands at 101, never dipping below 49. Buildings, deployables and all the rest of the world pushed its entity count as high as 146,918. 6,217 MB of memory was its top figure. Lag, to players, means low fps alongside an entity count on the rise.

What is the uptime of 【南瓜】Build-Test, and is it online?

Right now, 【南瓜】Build-Test is online. Its reported uptime suggests a restart roughly 5 days 13 hours ago. It was up 168 of 168 hours over the last 7 full days, 100% of the time. 13 September 2026 is when Rust Wipe Tracker first recorded it.

What Rust version is 【南瓜】Build-Test using?

Rust network protocol 2635 and build 168909 on Windows is what 【南瓜】Build-Test runs. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe schedule

How does 【南瓜】Build-Test handle its wipe days?

The average busiest point of its recent wipes was 24 players. 15 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held until the next wipe in 100% of recent wipes.

When does 【南瓜】Build-Test wipe? What schedule does it follow?

【南瓜】Build-Test wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. 5 days 18 hours have passed since this world was made.

Server tags

On Rust Wipe Tracker, which lists and filters is 【南瓜】Build-Test part of?

These Rust Wipe Tracker lists take 【南瓜】Build-Test: Rust build servers. On the server list, apply 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 and it appears.

How should you read the tags on 【南瓜】Build-Test?

The game's server browser picks up these 【南瓜】Build-Test tags: gmrust (Game mode): The game mode is standard Rust survival; mp101 (Max players): Slot count: 101; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): The region code is unset; ^k (Build server): Design and practise base building; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; EA (East Asia): In the server browser it appears under East Asia. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

How to join

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

Enter client.connect 45.125.45.246:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp101
Max players Slot count: 101.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code The region code is unset.

Gameplay

^k
Build server Design and practise base building.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.

Region

EA
East Asia In the server browser it appears 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.