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
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···WW··
·······
·······
·······
·······
·······
····
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.
usual gap0.3 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Fri 18 SepThu 17 Sep
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
Fri 18 Sep, 04:07 UTC41d ago
1
–
running
0
Thu 17 Sep, 20:32 UTC41d ago
1
–
0.3 days
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 reports the location a server gives; it does not check where the machine actually is. 183.50.202.247:28015 is the address to use.
Is 【南瓜-Build】 up, and how steady is its uptime?
At this moment, 【南瓜-Build】 is offline; the last time it was seen was 41 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 15 September 2026.
What Rust version is 【南瓜-Build】 on?
You will find 【南瓜-Build】 on Rust network protocol 2633 and build 162929, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does 【南瓜-Build】 wipe, and how often?
【南瓜-Build】 has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 41 days 13 hours have passed since this world was made.
What should you expect from wipe day on 【南瓜-Build】?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
Where does 【南瓜-Build】 place in the wider field of Rust servers?
Over the last seven days, 【南瓜-Build】 has #13,945 for player hours, in the top – of all ranked servers and #464 in Asia.
Is 【南瓜-Build】 a busy server?
The last sighting of 【南瓜-Build】 was 41 days 10 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on 【南瓜-Build】?
You'll see 【南瓜-Build】 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp51 (Max players): 51 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): This runs on build 162929; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^k (Build server): Design and practise your bases here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; EA (East Asia): You will find it under East Asia in the browser in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its 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.
Rules and settings
Which rules does 【南瓜-Build】 enforce, and what are its settings?
Nothing in the name of 【南瓜-Build】 states a gather rate. With no change from the game default, groups take up to 8 players. build & creative is the mode here, building in a sandbox, and no gathering. Under Community in the server browser you will find this community server. Oxide plugins are running on it. VAC, Valve's anti-cheat, is not enabled.
Connecting
How should you connect to 【南瓜-Build】?
Enter client.connect 183.50.202.247:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
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 players51 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Gameplay
^k
Build serverDesign and practise your bases here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
Region
EA
East AsiaYou will find it under East Asia in the browser.
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.