On the class lists: D (52), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#9,162top 41%
Last wipe4d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
59/ 100
C−
Working its way up from the back of the class: #9,162 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 99 server fps on average.
Wipeskeeping the crowd after a wipe
25/ 100
F
Needs to keep more players after wipe day: 25% of wipes kept half their crowd.
Momentumrank now against a week ago
83/ 100
B+
Climbing fast: up 6,011 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 41% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
·W··WWW
·····W·
····W·W
·····W·
·······
····W··
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held25%else halves by day 1
The first 48 hours of its last wipes
Fri 23 OctSat 10 OctSat 10 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, 21:33 UTC4d ago
1
–
running
0
Sat 10 Oct, 23:18 UTC17d ago
1
halved by day 1
12.9 days
0
Sat 10 Oct, 16:37 UTC17d ago
1
–
0.3 days
0
Sun 4 Oct, 13:14 UTC23d ago
1
halved by day 2
6.1 days
0
Fri 2 Oct, 09:10 UTC26d ago
1
✓ held half
2.2 days
0
Sat 26 Sep, 22:24 UTC31d ago
1
halved by day 1
5.4 days
1
Sun 20 Sep, 21:09 UTC37d ago
1
halved by day 1
6.1 days
1
Sat 19 Sep, 20:18 UTC38d ago
1
–
1 days
0
Fri 18 Sep, 20:21 UTC39d ago
1
–
1 days
0
Tue 15 Sep, 20:56 UTC42d ago
1
✓ held half
3 days
0
Tue 15 Sep, 00:36 UTC43d ago
1
–
0.8 days
0
Sun 13 Sep, 16:29 UTC44d ago
1
–
1.3 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
You'll find no region listed by Dustsackies Test Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 75.133.62.211:28015.
How dependable is Dustsackies Test Server, and is it online at the moment?
The server is down: Dustsackies Test Server is offline now, with the last sighting 1 hours ago. According to its reported uptime, the last restart was about 22 hours ago. It was up 59% of the time over the last 7 full days, 99 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does Dustsackies Test Server perform well?
It averaged 99 server fps over the last 48 hours, with a low of 63. At its peak, it held 79,535 entities, including buildings, deployables and all else in the world. At its highest, it used 3,955 MB of memory. When fps is low and entities climb, that is lag to players.
What Rust version is Dustsackies Test Server on?
Rust network protocol 2635 and build 168909 on Windows is what Dustsackies Test Server runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Dustsackies Test Server wipe its map?
Dustsackies Test Server wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 4 days 12 hours have passed since this world was made.
What happens on Dustsackies Test Server when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 1 hours into the latest wipe. Half the peak held until the next wipe in 25% of its recent wipes. In the other wipes it slipped under half by day 1.
Player count
What position does Dustsackies Test Server hold in the rankings?
Over the last seven days, Dustsackies Test Server has #9,162 for player hours, in the top 41% of all ranked servers.
What does the population on Dustsackies Test Server look like?
The last sighting of Dustsackies Test Server was 1 hours ago, and it is offline right now. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 22:00 UTC, with an average of 1 players.
Tags
What do Dustsackies Test Server's tags stand for?
The game's browser takes its cue from the tags Dustsackies Test Server has set: gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): 50 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): 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; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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 Rust Server Score filters and lists feature Dustsackies Test Server?
Rust Server Score lists that include Dustsackies Test Server: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
Which rules does Dustsackies Test Server enforce, and what are its settings?
You will find no gather rate in the name of Dustsackies Test Server. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in 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 Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Dustsackies Test Server uses?
Dustsackies Test Server runs a game-generated procedural map at size 5,800, seed 1. 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 Dustsackies Test Server?
Enter client.connect 75.133.62.211: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 asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^z,^y
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max players50 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
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).