Element card · group Community · atomic number 955, its rank
【南瓜】Build-Test
Online EA 45.125.45.246:28015 checked 2h 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
Top 4% of all ranked servers, top 16% in EA. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 24, 15 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 22 Oct, 21:55 UTC5d ago | 24 | – | running | 1 |
| Mon 19 Oct, 01:15 UTC9d ago | 25 | held half | 3.9 days | 4 |
| Tue 13 Oct, 20:03 UTC14d ago | 23 | held half | 5.2 days | 0 |
| Mon 12 Oct, 09:06 UTC16d ago | 25 | – | 1.5 days | 15 |
| Sun 11 Oct, 17:55 UTC17d ago | 25 | – | 0.6 days | 2 |
| Thu 8 Oct, 13:33 UTC20d ago | 32 | held half | 3.2 days | 0 |
| Tue 6 Oct, 10:36 UTC22d ago | 24 | held half | 2.1 days | 12 |
| Fri 2 Oct, 04:30 UTC26d ago | 25 | held half | 4.3 days | 0 |
| Sun 27 Sep, 00:04 UTC31d ago | 31 | held half | 5.2 days | 5 |
| Wed 23 Sep, 21:05 UTC34d ago | 24 | held half | 3.1 days | 3 |
| Mon 21 Sep, 22:30 UTC36d ago | 33 | – | 1.9 days | 0 |
| Mon 21 Sep, 12:18 UTC37d ago | 30 | – | 0.4 days | 24 |
| Thu 17 Sep, 23:45 UTC40d ago | 27 | held half | 3.5 days | 3 |
| Sun 13 Sep, 16:19 UTC45d ago | 33 | held half | 4.3 days | 16 |
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 wipesQuick answers
from the figures on this pageMap and rules
What map is in play on 【南瓜】Build-Test?
【南瓜】Build-Test runs a procedural map of size 4,000 with seed 1361858059; the game generates it. The map repeats when size and seed match, and you can view it on RustMaps from this page.
What rules has 【南瓜】Build-Test set, and what settings are in force?
Nothing in the name of 【南瓜】Build-Test gives a gather rate. Groups top out at 8 players, the default for the game. Play runs as build & creative, no gathering: sandbox building. It appears under Community in the server browser. Plugins in use: Oxide. The VAC anti-cheat from Valve is disabled.
Server details
What region hosts 【南瓜】Build-Test?
The EA tag is how 【南瓜】Build-Test lists itself, in Asia. The location shown is the one a server states; Rust Data Lab does not check where the machine actually stands. Connect at 45.125.45.246:28015.
Which Rust version is 【南瓜】Build-Test on?
Rust network protocol 2635 and build 168909 on Windows is what 【南瓜】Build-Test uses. Joining requires the same protocol on your game; Steam takes care of updating it.
How dependable is 【南瓜】Build-Test for staying online?
Right now, 【南瓜】Build-Test is reachable. About 5 days 13 hours ago is when it last restarted, based on its uptime. For the last 7 full days, 168 of 168 hours were online, giving 100% uptime. It first appeared to Rust Data Lab on 13 September 2026.
Does 【南瓜】Build-Test hold a steady performance?
The last 48 hours show an average of 101 server fps and a minimum of 49. Buildings, deployables and everything else in the world added up to as many as 146,918 entities. Up to 6,217 MB of memory was used. Players feel lag when fps is low and the entity count climbs.
Wipe schedule
How often does a wipe happen on 【南瓜】Build-Test, and at what time?
There is no next wipe to predict for 【南瓜】Build-Test, which wipes at irregular times. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 5 days 16 hours ago the current world was made.
How does 【南瓜】Build-Test look on the day of a wipe?
At their busiest, recent wipes averaged 24 players. Peak numbers on the latest wipe came 15 hours in. Half that peak was held until the next wipe in 100% of recent wipes.
Tags, lists
What should you understand from the tags 【南瓜】Build-Test carries?
gmrust (Game mode): Survival in the standard Rust style; mp101 (Max players): Player slots: 101; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): It runs build 168909; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^k (Build server): Base building and practice are the focus; ^o (Oxide): Plugins run through Oxide (uMod); EA (East Asia): East Asia is where the browser lists this server: that is the tag list 【南瓜】Build-Test publishes, and the game's server browser reads it. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.
Which Rust Data Lab filters and lists does 【南瓜】Build-Test appear in?
The Rust Data Lab lists that include 【南瓜】Build-Test are: Rust build and creative servers. Applying these filters on the server list returns it: 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; Last wipe: In the last week; Players now: At least 10.
Player numbers
What position does 【南瓜】Build-Test hold among Rust servers?
【南瓜】Build-Test is #955 on seven-day player hours, #88 in Asia, and in the top 4% of all ranked servers.
How many players does 【南瓜】Build-Test have at the moment?
【南瓜】Build-Test currently shows 13 players across 101 slots. Averaged over the past week: 10 players, peaking at 28. The busiest point in the last 48 hours came at 13:00 UTC, averaging 25 players.
Getting on
How can you connect to 【南瓜】Build-Test?
Open the console with F1 in Rust and type client.connect 45.125.45.246:28015. The Launch Rust button on this page does the same job through Steam.