【南瓜-Build】
Offline EA 183.50.200.167:28015 checked 11d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 72% of all ranked servers, top 94% in EA. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes
- 24/ 101
- 16/ 100
- 15/ 50
- 1/ 188
- 1/ 150
- 0/ 30
Quick answers
Tags and search
Where does 【南瓜-Build】 appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include 【南瓜-Build】: Rust build and creative servers. Its entry appears under the 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.
What's the meaning of the tags on 【南瓜-Build】?
gmrust (Game mode): This is the standard Rust survival experience; mp51 (Max players): There are 51 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166494 (Build): This server runs build 166494; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code; ^k (Build server): Work on base designs and practise building; ^o (Oxide): The plugin framework here is Oxide (uMod); EA (East Asia): The server browser lists it under East Asia — that is the tag list 【南瓜-Build】 puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What location is 【南瓜-Build】 in?
Its location is Asia, according to the EA tag 【南瓜-Build】 displays. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 183.50.200.167:28015.
What's the uptime like for 【南瓜-Build】?
The server 【南瓜-Build】 is not reachable at the moment; the last sighting was 11 days 15 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 2 October 2026.
What is the Rust version for 【南瓜-Build】?
On Windows, 【南瓜-Build】 runs Rust network protocol 2634 and build 166494. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
What schedule does 【南瓜-Build】 follow for wipes?
The wipes recorded for 【南瓜-Build】 are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 16 days 5 hours ago.
Map and rules
What settings are in place on 【南瓜-Build】?
The name of 【南瓜-Build】 contains no gather rate. Up to 8 players per group, which is the default. It runs build & creative, build freely in a sandbox, no gathering needed. It sits under Community in the server browser: a community server. Plugins in use: Oxide. The server does not run Valve's anti-cheat, VAC.
Player count
Is 【南瓜-Build】 busy?
【南瓜-Build】 was last seen 11 days 15 hours ago and is offline as you read this.
What's 【南瓜-Build】's rank among Rust servers?
Over the last seven days, 【南瓜-Build】 sits at #16,008 by player hours, among the top 72% of all ranked servers and #491 in Asia.
Join info
What's the process to join 【南瓜-Build】?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 183.50.200.167:28015.