Working its way up from the back of the class: #15,159 on player hours.
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
52/ 100
D
Moving up: up 690 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
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
homeserver build test leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 80.187.123.34:28015.
How reliable is homeserver build test, and is it up?
At this moment, homeserver build test is offline; the last time it was seen was 10 days 4 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 17 October 2026.
On what Rust version does homeserver build test sit?
You will find homeserver build test on Rust network protocol 2634 and build 167781, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does homeserver build test reset?
homeserver build test has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 10 days 4 hours have passed since this world was made.
Player numbers
Where does homeserver build test place in the wider field of Rust servers?
In the top 70% of all ranked servers, homeserver build test sits at #15,159 for player hours over the last seven days.
What does the population on homeserver build test look like?
The last sighting of homeserver build test was 10 days 4 hours ago, and it is offline right now.
Tags
How should you read the tags on homeserver build test?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp4 (Max players): 4 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon are the tags homeserver build test publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does homeserver build test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include homeserver build test: Modded Rust servers, graded and Rust build and creative servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is homeserver build test set up, and what rules does it keep?
Nothing in the name of homeserver build test states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
homeserver build test runs which map?
A procedural map, generated by the game, is what homeserver build test runs.
How to join
How do you get onto homeserver build test?
Enter client.connect 80.187.123.34: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 asmp4,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp4
Max players4 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonPlugin framework: Carbon.
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 momentum (D); standing is the one to work on (F).