Working its way up from the back of the class: #15,508 on player hours.
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
26/ 100
F
Lost ground: down 7,526 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
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
Top 71% of all ranked servers, top 89% in EA. Ranked on player hours over the last seven days.
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
Wed 23 Sep, 18:49 UTC35d ago
1
–
running
0
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
In Asia, according to its own listing, sits 【南瓜-Build】, with the EA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. 183.50.200.8:28015 is the address to use.
How reliable is 【南瓜-Build】, and is it up?
The server is down: 【南瓜-Build】 is offline now, with the last sighting 35 days ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 22 September 2026, Rust Server Score saw it for the first time.
On what Rust version does 【南瓜-Build】 sit?
Rust network protocol 2633 and build 162929 on Windows is what 【南瓜-Build】 runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does 【南瓜-Build】 wipe, and how often?
There are too few wipes on record for 【南瓜-Build】 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 35 days 2 hours.
What should you expect from wipe day on 【南瓜-Build】?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Population
Where does 【南瓜-Build】 place in the wider field of Rust servers?
Over the last seven days, 【南瓜-Build】 has #15,508 for player hours, in the top 71% of all ranked servers and #473 in Asia.
How many players does 【南瓜-Build】 usually have?
The last sighting of 【南瓜-Build】 was 35 days ago, and it is offline right now.
Lists and filters
How should you read the tags on 【南瓜-Build】?
The game's browser takes its cue from the tags 【南瓜-Build】 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp51 (Max players): The server holds 51 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): Build number: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^k (Build server): Design and practise your bases here; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): In the server browser it appears 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.
Which Rust Server Score filters and lists feature 【南瓜-Build】?
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】?
The name of 【南瓜-Build】 gives no gather rate. With no change from the game default, groups take up to 8 players. build & creative is the mode here, no gathering: sandbox building instead. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. VAC, Valve's anti-cheat, is not enabled.
Connecting
How should you connect to 【南瓜-Build】?
To connect, start Rust, press F1, and type client.connect 183.50.200.8: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 modeRust survival, played by the standard rules.
mp51
Max playersThe server holds 51 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildBuild number: 162929.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Gameplay
^k
Build serverDesign and practise your bases here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
EA
East AsiaIn 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.
A term to build on. Even marks across the subjects, from F to F.