RUST METRICSFlight deck · live data
Data live Servers11,737 Players52,204 Populated3,347 Fresh wipes 3 h125 Scan5 min
‹ All servers45.125.45.246:28015
Online Full Queue Fresh wipe Wipe due No query

【南瓜】Build-Test

Online EA 45.125.45.246:28015 checked 9m ago

oxide
COM 1 · connect

Server instruments

last reading Wed 22:00 UTC
0 25 50 76 101 PAX 1 /101

Players now

1% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 133 SERVER FPS

Server fps

48 h low 49 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 134,651 ×1000

Entities

48 h range 131,399–146,918 · memory 5,750 MB
1239 ET SINCE RESTART 5D 19H

Uptime

5 days 19 hours since its last restart, at the last reading
7-day average10peak 28
Rank#951top 4% · #88 in EA
Last wipe5d agono schedule published
Next wipe–no rhythm it keeps
Memory5,750MB48 h peak 28 players
REC 1

Players

AveragePeak
01020304000:0009:0018:0003:0012:0022:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020000:0009:0018:0003:0012:0022: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.

REC 3

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.

PLAN

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 21:55 UTC6d ago 24 – running 1
Mon 19 Oct, 01:15 UTC9d 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 UTC26d ago 25 held half 4.3 days 0
Sun 27 Sep, 00:04 UTC31d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on 【南瓜】Build-Test when wipe day comes?

At their busiest, its recent wipes drew 24 players on average. After the latest wipe, numbers topped out at 15 hours. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

How often does 【南瓜】Build-Test wipe, and when?

No next wipe can be predicted for 【南瓜】Build-Test, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 5 days 21 hours ago.

Tags

Which tags does 【南瓜】Build-Test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp101 (Max players): The server holds 101 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^k (Build server): Design bases and practise building; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; EA (East Asia): The server browser files it under East Asia from 【南瓜】Build-Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does 【南瓜】Build-Test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring 【南瓜】Build-Test: Build and creative servers. These filters bring it up on the server list: 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.

Occupancy

What position does 【南瓜】Build-Test hold among Rust servers?

Player hours over the last seven days put 【南瓜】Build-Test at #951, #88 in Asia, in the top 4% of all ranked servers.

What player count does 【南瓜】Build-Test carry?

1 of 101 slots are filled on 【南瓜】Build-Test right now. Check: players over seven days. Average 10, peak 28. The last 48 hours peaked at 13:00 UTC, averaging 25 players at that hour.

Server

What location is 【南瓜】Build-Test hosted in?

Its EA tag places 【南瓜】Build-Test in Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 45.125.45.246:28015.

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

Rust network protocol 2635 and build 168909 on Windows is the build 【南瓜】Build-Test runs. Matching protocol is required to join. Let Steam update your game.

Is performance on 【南瓜】Build-Test within range?

Over the last 48 hours the average was 100 server fps; the floor was 49. Peak entity count: 146,918. Buildings, deployables and all else included. Reading: 6,217 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.

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

Check: connection. 【南瓜】Build-Test is online at this moment. Check: restart. The uptime it reports puts the last restart about 5 days 19 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

How is 【南瓜】Build-Test configured, and what rules are in force?

Reading the name gives no gather rate for 【南瓜】Build-Test. No limit is set beyond the default. Groups take up to 8 players. The mode is build & creative. Note the following: no gathering; sandbox building instead. The server browser lists it under Community. Plugin count: Oxide. Anti-cheat reading: VAC off, Valve's system.

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

From seed 1361858059, the game generates the procedural map on 【南瓜】Build-Test. Its size is 4,000. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How can you get onto 【南瓜】Build-Test?

Check: join. Open Rust, press F1, then enter client.connect 45.125.45.246:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp101
Max players The server holds 101 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Gameplay

^k
Build server Design bases and practise building.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.

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.