Working its way up from the back of the class: #15,101 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
30/ 100
F
Lost ground: down 6,106 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.
AveragePeak
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 68% of all ranked servers, top 92% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 183.50.200.127:28015.
Is 【南瓜-Build】 up, and how steady is its uptime?
The server is down: 【南瓜-Build】 is offline now, with the last sighting 21 days 5 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 6 October 2026, Rust Server Score saw it for the first time.
What Rust version is 【南瓜-Build】 on?
You will find 【南瓜-Build】 on Rust network protocol 2634 and build 166494, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does 【南瓜-Build】 reset?
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 27 days 14 hours.
Population
Where does 【南瓜-Build】 place in the wider field of Rust servers?
Over the last seven days, 【南瓜-Build】 has #15,101 for player hours, in the top 68% of all ranked servers and #482 in Asia.
How many players does 【南瓜-Build】 usually have?
The last sighting of 【南瓜-Build】 was 21 days 5 hours ago, and it is offline right now.
Tags
What is meant by the tags on 【南瓜-Build】?
gmrust (Game mode): Survival in the standard Rust style; mp51 (Max players): Its slot count is 51; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): This runs on build 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^k (Build server): Bases can be designed and practised here; ^o (Oxide): The plugin framework in use is Oxide (uMod); EA (East Asia): In the server browser it appears under East Asia are the tags 【南瓜-Build】 publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
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. You can find it under these server-list filters: 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
How is 【南瓜-Build】 set up, and what rules does it keep?
You will find no gather rate in the name of 【南瓜-Build】. The group limit stays at the game's default of 8 players. build & creative is the mode here, no gathering: sandbox building instead. Under Community in the server browser you will find this community server. Plugins on it number Oxide. The server does not run VAC, Valve's anti-cheat.
Connecting
How do you get onto 【南瓜-Build】?
Enter client.connect 183.50.200.127: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?,v2634,^k,EA,gmrust,cs166494,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp51
Max playersIts slot count is 51.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Gameplay
^k
Build serverBases can be designed and practised here.
Mods and access
^o
OxideThe plugin framework in use is 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.