Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
The EA tag on 【南瓜-Build】 puts it in Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. 183.50.200.253:28015 is the address to use.
How reliable is 【南瓜-Build】, and is it up?
At this moment, 【南瓜-Build】 is offline; the last time it was seen was 44 days 10 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is 【南瓜-Build】 running?
You will find 【南瓜-Build】 on Rust network protocol 2633 and build 162929, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does 【南瓜-Build】 wipe, and how often?
There are too few wipes on record for 【南瓜-Build】 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 44 days 13 hours have passed since this world was made.
What happens on 【南瓜-Build】 when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Population
Where does 【南瓜-Build】 place in the wider field of Rust servers?
Over the last seven days, 【南瓜-Build】 has #15,025 for player hours, in the top – of all ranked servers and #490 in Asia.
How many players does 【南瓜-Build】 usually have?
The last sighting of 【南瓜-Build】 was 44 days 10 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on 【南瓜-Build】?
The game's browser takes its cue from the tags 【南瓜-Build】 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp51 (Max players): The server holds 51 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs162929 (Build): The game build is 162929; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^k (Build server): Use it to plan and practise base builds; ^o (Oxide): Oxide (uMod) provides the plugin framework here; EA (East Asia): The server browser lists it under East Asia. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does 【南瓜-Build】 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count 【南瓜-Build】 among them: Rust build and creative servers. It shows under the following filters 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.
Map and rules
What settings and rules apply on 【南瓜-Build】?
Nothing in the name of 【南瓜-Build】 states a gather rate. The default of 8 players applies as the group cap. build & creative is the mode here, no gathering, just sandbox building. You will see it in the Community section of the server browser, since it is a community server. Oxide plugins are running on it. The server does not run VAC, Valve's anti-cheat.
How to join
How should you connect to 【南瓜-Build】?
To connect, start Rust, press F1, and type client.connect 183.50.200.253:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp51,ptrak,$r?,v2633,^k,EA,gmrust,cs162929,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp51
Max playersThe server holds 51 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs162929
BuildThe game build is 162929.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Gameplay
^k
Build serverUse it to plan and practise base builds.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
Region
EA
East AsiaThe server browser lists 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.
Not enough figures yet to write a report. Check back after a few days on the list.