StatusLive Servers online11,614 Players32,078 Populated2,758 Wiped · 3 h69 Interval5 min Date29 OCT 2026

DWG RG-S15025Server sheetchecked 44d ago

【南瓜-Build】

Offline EA 183.50.200.253:28015 checked 44d ago

oxide
Connect
Players now 0/ 51 0% full
7-day average0peak –
Rank#15,025#490 in EA
Last wipe44d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on 【南瓜-Build】
Fig. 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep
Fig. 3Rank on player hours, daily
Schedule

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 peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 14 Sep, 13:24 UTC44d ago 1 – running 1

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
【南瓜】Build-TestEA · groups of 8+ · 10 on average
12 / 101
02
Intoxicated SEA Sandbox - Creative | Build | NoclipEA · groups of 8+ · 10 on average
16 / 100
03 15 / 50
04 1 / 188
05
風紀委員 堤防部EA · groups of 8+ · 1 on average
0 / 30
06
【开心萌橙PVE-kxmc】休闲娱乐/5倍/防抄家/任务EA · groups of 20+ · monthly · 2 on average
2 / 150
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for 【南瓜-Build】, and is it up?

Last seen 44 days 13 hours ago; right now 【南瓜-Build】 is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.

In which location is 【南瓜-Build】 hosted?

In Asia 【南瓜-Build】 lists itself, tagged EA. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 183.50.200.253:28015.

What Rust version is recorded for 【南瓜-Build】?

The platform is Windows and the version is Rust network protocol 2633 and build 162929 on 【南瓜-Build】. To join, your game must be on the same protocol; Steam handles the update.

Player data

What player count is recorded on 【南瓜-Build】?

No response from 【南瓜-Build】; the server was last seen 44 days 13 hours ago.

Against other Rust servers, where is 【南瓜-Build】 placed?

【南瓜-Build】 also measures #490 in Asia on the same seven-day player-hour count, at #15,025 globally and in the top – of ranked servers.

Wipe times

What is recorded on 【南瓜-Build】 on wipe day?

At their busiest, its recent wipes drew 1 players on average. At 0 hours after the latest wipe the crowd was at its peak.

On 【南瓜-Build】, when do wipes occur?

【南瓜-Build】's rhythm cannot be told yet: too few of its wipes are on record. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The current world has been in use since 44 days 16 hours ago.

Map and rules

What settings and rules apply on 【南瓜-Build】?

No gather rate is stated in the name of 【南瓜-Build】. No limit is published beyond the default: 8 players per group. build & creative, sandbox building, no gathering, is the game mode. The server browser lists it under Community. The plugin count is Oxide. Anti-cheat: VAC, from Valve, is off.

Filters

On Rust Graphs, which lists and filters contain 【南瓜-Build】?

These Rust Graphs lists include 【南瓜-Build】: Rust build servers, plotted live. On the server list, these filters bring it up: 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.

On 【南瓜-Build】, what is meant by each tag?

The game's server browser reads these tags from 【南瓜-Build】: gmrust (Game mode): Standard survival, as Rust plays; mp51 (Max players): 51 player slots; ts8 (Group limit): The default team size of 8 applies; v2633 (Protocol): Your game must match protocol 2633 to join; cs162929 (Build): 162929 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^k (Build server): Design and practise bases here; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): The browser's listing places it under East Asia. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Joining the server

How is 【南瓜-Build】 joined?

Enter client.connect 183.50.200.253:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp51,ptrak,$r?,v2633,^k,EA,gmrust,cs162929,ts8,^o

Game

gmrust
Game mode Standard survival, as Rust plays.
mp51
Max players 51 player slots.
ts8
Group limit The default team size of 8 applies.
v2633
Protocol Your game must match protocol 2633 to join.
cs162929
Build 162929 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Gameplay

^k
Build server Design and practise bases here.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).

Region

EA
East Asia The browser's listing places 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.

KeyTag string decoded