On the class lists: D (46), with population over 48 hours and no performance mark.
Players now0/ 200% full
7-day average0peak 1
Rank#9,552top 43%
Last wipe4d agoweekly schedule
Next wipe2d 8hFri 30 Oct, 19:52 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 20 on average. Plenty of space to grow.
Standingrank on player hours
57/ 100
C−
Working its way up from the back of the class: #9,552 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: 84 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
79/ 100
B
Climbing fast: up 5,621 places this week.
A fair term, with more to come.
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 43% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·W·····
·······
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 19:52 UTC, in 2d 8h.
Its weekly schedule tag · low confidence
usual gap11 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
2d 8hFri 30 Oct, 19:52 UTC
8d 7hThu 5 Nov, 19:00 UTCFW
9d 8hFri 6 Nov, 19:52 UTC
16d 8hFri 13 Nov, 19:52 UTC
23d 8hFri 20 Nov, 19:52 UTC
30d 8hFri 27 Nov, 19:52 UTC
36d 7hThu 3 Dec, 19:00 UTCFW
37d 8hFri 4 Dec, 19:52 UTC
The first 48 hours of its last wipes
Fri 23 OctTue 6 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 19:52 UTC4d ago
1
–
running
0
Tue 6 Oct, 15:24 UTC21d ago
1
halved by day 1
17.2 days
1
Thu 1 Oct, 18:35 UTCFW26d ago
2
halved by day 1
4.9 days
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
No region is published for Rust Buds [Solo/Duo]. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 116.202.51.49:28065.
How reliable is Rust Buds [Solo/Duo], and is it up?
You can join now: Rust Buds [Solo/Duo] is online. The uptime it reports puts the last restart at about 8 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does Rust Buds [Solo/Duo] perform well?
It averaged 84 server fps over the last 48 hours, with a low of 67. At its peak, it held 121,485 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,482 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is Rust Buds [Solo/Duo] on?
Rust network protocol 2635 and build 168909 on Linux is what Rust Buds [Solo/Duo] runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does Rust Buds [Solo/Duo] reset?
Its tag sets the prediction, as the record holds too few of Rust Buds [Solo/Duo]'s wipes to confirm its schedule. Friday 30 October at 19:52 UTC is the date set for its next wipe. 4 days 15 hours have passed since this world was made. Its tags state that it wipes weekly.
What happens on Rust Buds [Solo/Duo] when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 1 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player numbers
What position does Rust Buds [Solo/Duo] hold in the rankings?
Over the last seven days, Rust Buds [Solo/Duo] has #9,552 for player hours, in the top 43% of all ranked servers.
What does the population on Rust Buds [Solo/Duo] look like?
Right now, 0 players are on Rust Buds [Solo/Duo], which has 20 slots. It peaked at 1 and averaged 0 players over the last seven days.
Tags
How should you read the tags on Rust Buds [Solo/Duo]?
The game's browser takes its cue from the tags Rust Buds [Solo/Duo] has set: gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): The server holds 20 slots; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^q (Premium): You need Rust's premium status to get in; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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.
Where does Rust Buds [Solo/Duo] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Rust Buds [Solo/Duo]: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: Premium; Server tag: Weekly ^w, Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.
Server rules
Which rules does Rust Buds [Solo/Duo] enforce, and what are its settings?
The name of Rust Buds [Solo/Duo] gives no gather rate. The group limit stays at the game's default of 8 players. 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. Plugins on it number Oxide. You need Rust's premium status to get in. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Rust Buds [Solo/Duo]?
A procedural map of size 4,500 and seed 1057629265, generated by the game, is what Rust Buds [Solo/Duo] runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to Rust Buds [Solo/Duo]?
To connect, start Rust, press F1, and type client.connect 116.202.51.49:28065. Or click Launch Rust here, which launches Rust through Steam and joins you. You need Rust's premium status to get in.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2635,^w,gmrust,cs168909,^q,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersThe server holds 20 slots.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^q
PremiumYou need Rust's premium status to get in.
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).