On the class lists: B− (71), with population over 48 hours and no performance mark.
Players now26/ 10126% full
7-day average10peak 28
Rank#958top 4% · #87 in EA
Last wipe5d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
10/ 100
F
A quiet classroom so far: 10 of 101 on average. Plenty of space to grow.
Standingrank on player hours
96/ 100
A+
Well up the rankings: #958 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 102 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
54/ 100
D
Moving up: up 86 places this week.
A good term.
Strongest in performance (A+); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 4% of all ranked servers, top 16% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
13 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
···W···
W·W···W
····W··
·W·W··W
WW·····
W··W···
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.5 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak24players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Thu 22 OctMon 19 OctTue 13 Oct
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 UTC16d 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 UTC44d 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
classmates: the same kind of game, then region, group limit, rate and wipes
In Asia, according to its own listing, sits 【南瓜】Build-Test, with the EA tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 45.125.45.246:28015.
How dependable is 【南瓜】Build-Test, and is it online at the moment?
You can join now: 【南瓜】Build-Test is online. According to its reported uptime, the last restart was about 5 days 7 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Is 【南瓜】Build-Test smooth to play on?
It never fell below 49 server fps in the last 48 hours, averaging 102. Up to 154,236 entities were in the world, covering buildings, deployables and the rest. Up to 6,212 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is 【南瓜】Build-Test on?
Rust network protocol 2635 and build 168909 on Windows is what 【南瓜】Build-Test runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does 【南瓜】Build-Test wipe, and how often?
No next wipe can be predicted for 【南瓜】Build-Test, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 5 days 13 hours.
What happens on 【南瓜】Build-Test when wipe day arrives?
The average peak on its recent wipes was 24 players. The crowd on the latest wipe was largest 15 hours after it began. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player numbers
What position does 【南瓜】Build-Test hold in the rankings?
Over the last seven days, 【南瓜】Build-Test has #958 for player hours, in the top 4% of all ranked servers and #87 in Asia.
Is 【南瓜】Build-Test a busy server?
【南瓜】Build-Test is showing 26 players right now, with 101 slots in total. It peaked at 28 and averaged 10 players over the last seven days. Over the last 48 hours, the peak hour was 13:00 UTC, averaging 25 players.
Lists and filters
How should you read the tags on 【南瓜】Build-Test?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp101 (Max players): Its slot count is 101; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^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 are the tags 【南瓜】Build-Test 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.
Which Rust Server Score filters and lists feature 【南瓜】Build-Test?
These Rust Server Score lists count 【南瓜】Build-Test among them: Rust build and creative servers. These filters bring it up 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; Last wipe: In the last week; Players now: At least 10.
Rules and settings
What settings and rules apply on 【南瓜】Build-Test?
You will find no gather rate in the name of 【南瓜】Build-Test. With no change from the game default, groups take up to 8 players. You get build & creative here, no gathering: sandbox building instead. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map 【南瓜】Build-Test uses?
A procedural map of size 4,000 and seed 1361858059, generated by the game, is what 【南瓜】Build-Test runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join 【南瓜】Build-Test?
Enter client.connect 45.125.45.246: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 asmp101,ptrak,$r?,v2635,^k,EA,gmrust,cs168909,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp101
Max playersIts slot count is 101.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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.
A good term. Strongest in performance (A+); population is the one to work on (F).