Working its way up from the back of the class: #15,258 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 591 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, and #528 of the trio servers (top 85%). 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
You'll find no region listed by BASEGEN LOCAL TEST. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 187.13.12.104:28015.
Is BASEGEN LOCAL TEST up, and how steady is its uptime?
At this moment, BASEGEN LOCAL TEST is offline; the last time it was seen was 11 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 17 October 2026.
On what Rust version does BASEGEN LOCAL TEST sit?
Rust network protocol 2634 and build 167781 on Windows is what BASEGEN LOCAL TEST runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does BASEGEN LOCAL TEST wipe its map?
The record holds too few of BASEGEN LOCAL TEST's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 11 days 12 hours.
Player count
What position does BASEGEN LOCAL TEST hold in the rankings?
Over the last seven days, BASEGEN LOCAL TEST has #15,258 for player hours, in the top 70% of all ranked servers. In the trio group, it ranks #528.
Is BASEGEN LOCAL TEST a busy server?
It has been 11 days 3 hours since BASEGEN LOCAL TEST was last seen, and it is offline right now.
Tags and filters
What is meant by the tags on BASEGEN LOCAL TEST?
The game's browser takes its cue from the tags BASEGEN LOCAL TEST has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): 10 slots are available; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature BASEGEN LOCAL TEST?
Rust Server Score lists that include BASEGEN LOCAL TEST: Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Trio; Last wipe: In the last 2 weeks.
Map and rules
What settings and rules apply on BASEGEN LOCAL TEST?
The name of BASEGEN LOCAL TEST gives no gather rate. The cap on group size is 3 players (trio). It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on BASEGEN LOCAL TEST?
BASEGEN LOCAL TEST runs a procedural map, which the game generates.
Connecting
How do you get onto BASEGEN LOCAL TEST?
To connect, start Rust, press F1, and type client.connect 187.13.12.104:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max players10 slots are available.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 momentum (D); standing is the one to work on (F).