Working its way up from the back of the class: #13,882 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
41/ 100
F
Slipped a little: down 2,481 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
AveragePeakWipe
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 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 00:35 UTC24d ago
1
–
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
No region is published for Shimeji's Test Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 153.173.2.5:28015.
Is Shimeji's Test Server up, and how steady is its uptime?
At this moment, Shimeji's Test Server is offline; the last time it was seen was 24 days ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Shimeji's Test Server sit?
The server Shimeji's Test Server is on Rust network protocol 2634 and build 166652 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does Shimeji's Test Server wipe its map?
There are too few wipes on record for Shimeji's Test Server to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 24 days 3 hours.
What should you expect from wipe day on Shimeji's Test Server?
The average peak on its recent wipes was 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does Shimeji's Test Server sit among Rust servers?
Over the last seven days, Shimeji's Test Server has #13,882 for player hours, in the top 61% of all ranked servers.
How many players does Shimeji's Test Server usually have?
The last sighting of Shimeji's Test Server was 24 days ago, and it is offline right now.
Tags and filters
How should you read the tags on Shimeji's Test Server?
The game's browser takes its cue from the tags Shimeji's Test Server has set: gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): 1 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; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here. 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 Shimeji's Test Server?
These Rust Server Score lists count Shimeji's Test Server among them: 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.
Map and rules
How is Shimeji's Test Server set up, and what rules does it keep?
The name of Shimeji's Test Server gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode 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. You are covered by VAC, Valve's anti-cheat.
How to join
How should you connect to Shimeji's Test Server?
To connect, start Rust, press F1, and type client.connect 153.173.2.5:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max players1 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.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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. Even marks across the subjects, from F to F.