On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now3/ 1202% full
7-day average1peak 4
Rank#3,500top 16%
Last wipe27d agomonthly schedule
Next wipe7d 23hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 120 on average. Plenty of space to grow.
Standingrank on player hours
84/ 100
B+
Holds a respectable place: #3,500 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
23/ 100
F
Needs to work on its frame rate: 14 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
41/ 100
F
Slipped a little: down 637 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
No five-minute samples in the last two hours.
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 16% of all ranked servers, and #212 of the duo servers (top 51%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h.
The force wipe · high confidence
wipe-day peak7players, last three wipes
Coming wipes
7d 23hThu 5 Nov, 19:00 UTCFW
35d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 7, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:10 UTCFW27d ago
7
–
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
In what location does TIRust BattleBay Solo/Duo Minis|Low Upkeep sit?
TIRust BattleBay Solo/Duo Minis|Low Upkeep leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 64.40.8.248:28015.
Is TIRust BattleBay Solo/Duo Minis|Low Upkeep up, and how steady is its uptime?
The server is up: TIRust BattleBay Solo/Duo Minis|Low Upkeep is online now. The uptime it reports puts the last restart at about 5 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does TIRust BattleBay Solo/Duo Minis|Low Upkeep perform well?
The average over the last 48 hours was 14 server fps, and it never went below 3. At its peak, it held 94,741 entities, including buildings, deployables and all else in the world. Up to 3,120 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does TIRust BattleBay Solo/Duo Minis|Low Upkeep sit?
The server TIRust BattleBay Solo/Duo Minis|Low Upkeep is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does TIRust BattleBay Solo/Duo Minis|Low Upkeep wipe, and how often?
TIRust BattleBay Solo/Duo Minis|Low Upkeep wipes with the force wipe and at no other time. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 27 days 1 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What should you expect from wipe day on TIRust BattleBay Solo/Duo Minis|Low Upkeep?
Recent wipes have peaked at 7 players on average. Peak numbers came 4 hours into the latest wipe.
Player numbers
Where does TIRust BattleBay Solo/Duo Minis|Low Upkeep sit among Rust servers?
Over the last seven days, TIRust BattleBay Solo/Duo Minis|Low Upkeep has #3,500 for player hours, in the top 16% of all ranked servers. It comes #212 among servers in the duo group.
Is TIRust BattleBay Solo/Duo Minis|Low Upkeep a busy server?
Right now, 3 players are on TIRust BattleBay Solo/Duo Minis|Low Upkeep, which has 120 slots. The seven-day average is 1 players, with a peak of 4. Over the last 48 hours, the peak hour was 17:00 UTC, averaging 3 players.
Lists and filters
What is meant by the tags on TIRust BattleBay Solo/Duo Minis|Low Upkeep?
You'll see TIRust BattleBay Solo/Duo Minis|Low Upkeep tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp120 (Max players): The server holds 120 slots; ts2 (Group limit): No team may go above 2; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; rustmaps (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one in the browser, which picks them up from the server. 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 person or group runs TIRust BattleBay Solo/Duo Minis|Low Upkeep?
The same operator most likely runs TIRust BattleBay Solo/Duo Minis|Low Upkeep and the 3 other servers we track that also publish a tirust.fun hostname.
Which lists and filters on Rust Server Score show TIRust BattleBay Solo/Duo Minis|Low Upkeep?
These Rust Server Score lists count TIRust BattleBay Solo/Duo Minis|Low Upkeep among them: Duo servers, marked like a report and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Monthly.
Server rules
How is TIRust BattleBay Solo/Duo Minis|Low Upkeep set up, and what rules does it keep?
Nothing in the name of TIRust BattleBay Solo/Duo Minis|Low Upkeep states a gather rate. The cap on group size is 2 players (duo). You get survival here, gather, build and raid, as in 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. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
TIRust BattleBay Solo/Duo Minis|Low Upkeep runs which map?
A custom map of size 3,875 is in use on TIRust BattleBay Solo/Duo Minis|Low Upkeep, and its published file can be downloaded from this page.
How to join
How should you connect to TIRust BattleBay Solo/Duo Minis|Low Upkeep?
Enter client.connect 64.40.8.248:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://tirust.fun.
Server tags
what each one means
Published asmp120,ptrak,$r?,v2635,^m,gmrust,cs168909,ts2,^o^z,rustmaps
Game
gmrust
Game modeRust survival, played by the standard rules.
mp120
Max playersThe server holds 120 slots.
ts2
Group limitNo team may go above 2.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Other
rustmaps
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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).