On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak –
Rank#15,327top 69%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,327 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
67/ 100
C+
Slows down under load at times: 40 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 202 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 22:02 UTC26d ago
0
–
running
0
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
You'll find no region listed by Build Contest. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 64.20.40.98:27058 is the address to use.
Is Build Contest up, and how steady is its uptime?
You can join now: Build Contest is online. The uptime it reports puts the last restart at about 17 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
How well does Build Contest run?
The average over the last 48 hours was 40 server fps, and it never went below 40. Buildings, deployables and everything else in the world added up to as many as 66,206 entities. At its highest, it used 2,396 MB of memory. Players feel lag when fps drops and entities pile up.
On what Rust version does Build Contest sit?
Rust network protocol 2635 and build 168909 on Linux is what Build Contest runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Build Contest wipe its map?
The record holds too few of Build Contest's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 26 days 19 hours.
What happens on Build Contest when wipe day arrives?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
Where does Build Contest sit among Rust servers?
Over the last seven days, Build Contest has #15,327 for player hours, in the top 69% of all ranked servers.
What does the population on Build Contest look like?
Build Contest is showing 0 players right now, with 40 slots in total. Over the past seven days, the average player count was 0.
Tags and filters
How should you read the tags on Build Contest?
The game's browser takes its cue from the tags Build Contest has set: gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): 40 slots are available; 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): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^c (Creative): No gathering here: it is a sandbox where you build what you want; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Build Contest?
These Rust Server Score lists count Build Contest among them: Modded Rust servers, graded, Rust build and creative servers and Rust creative servers, scored and graded. These filters bring it up on the server list: Type: Modded; Server tag: Creative ^c, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is Build Contest set up, and what rules does it keep?
The name of Build Contest gives no gather rate. The default of 8 players applies as the group cap. You get build & creative here, no gathering: sandbox building instead. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Build Contest runs which map?
Build Contest runs a game-generated procedural map at size 3,500, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
Getting in
How do you get onto Build Contest?
To connect, start Rust, press F1, and type client.connect 64.20.40.98:27058. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/Yk2bBhmVwP.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,^c,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max players40 slots are available.
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
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Gameplay
^c
CreativeNo gathering here: it is a sandbox where you build what you want.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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. Strongest in uptime (A+); population is the one to work on (F).