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.
No daily history yet.
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
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#1】 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 45.125.45.246:28035.
How reliable is 【南瓜-Build#1】, and is it up?
You cannot join now: 【南瓜-Build#1】 is offline, last seen 44 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 14 September 2026.
Which Rust version is 【南瓜-Build#1】 running?
The server 【南瓜-Build#1】 is on Rust network protocol 2633 and build 162929 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does 【南瓜-Build#1】 wipe, and how often?
The record holds too few of 【南瓜-Build#1】's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 44 days 8 hours.
Population
Where does 【南瓜-Build#1】 place in the wider field of Rust servers?
Over the last seven days, 【南瓜-Build#1】 has #12,835 for player hours, in the top – of all ranked servers and #470 in Asia.
What does the population on 【南瓜-Build#1】 look like?
The last sighting of 【南瓜-Build#1】 was 44 days 6 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on 【南瓜-Build#1】?
The game's browser takes its cue from the tags 【南瓜-Build#1】 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp81 (Max players): The server holds 81 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): This runs on build 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $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): The server browser lists it under East Asia. 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#1】 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include 【南瓜-Build#1】: 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.
Server rules
How is 【南瓜-Build#1】 set up, and what rules does it keep?
Nothing in the name of 【南瓜-Build#1】 states a gather rate. The group limit stays at the game's default of 8 players. You get build & creative here, no gathering, just sandbox building. You will see it in the Community section of the server browser, since it is a community server. The plugin count runs to Oxide. The server does not run VAC, Valve's anti-cheat.
Connecting
What is the way to join 【南瓜-Build#1】?
Enter client.connect 45.125.45.246:28035 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 asmp81,ptrak,$r?,v2633,^k,EA,gmrust,cs162929,ts8,^o
Game
gmrust
Game modeRust survival, played by the standard rules.
mp81
Max playersThe server holds 81 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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 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.