On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now0/ ?
7-day average0peak –
Rank#15,339top 69%
Last wipe25d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,339 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
50/ 100
D
Slows down under load at times: 30 server fps on average.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 166 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in uptime (A+); 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
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W·WW·W·
WWWW···
·······
·······
···
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 gap1 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 1
The first 48 hours of its last wipes
Thu 8 OctWed 7 OctTue 6 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in, with 1 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 01:32 UTC20d ago
1+1 queue
–
running
0
Wed 7 Oct, 04:47 UTC21d ago
1+1 queue
–
0.9 days
0
Tue 6 Oct, 01:05 UTC22d ago
1+1 queue
–
1.2 days
0
Mon 5 Oct, 18:42 UTC23d ago
1+1 queue
–
0.3 days
0
Sat 3 Oct, 10:20 UTC25d ago
1+1 queue
✓ held half
2.3 days
0
Thu 1 Oct, 08:13 UTC27d ago
2+1 queue
halved by day 1
2.1 days
1
Thu 1 Oct, 02:12 UTC27d ago
2+1 queue
–
0.3 days
0
Wed 30 Sep, 08:48 UTC28d ago
2+1 queue
–
0.7 days
0
Mon 28 Sep, 09:45 UTC30d ago
1+1 queue
–
2 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
Server Has Moved! leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 23.27.211.226:28018 is the address to use.
Is Server Has Moved! up, and how steady is its uptime?
Right now, Server Has Moved! is online. About 14 days 12 hours ago, it restarted, based on the uptime it reports. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does Server Has Moved! run?
It averaged 30 server fps over the last 48 hours, with a low of 30. At its peak, it held 8,347 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,559 MB. Players feel lag when fps drops and entities pile up.
What Rust version is Server Has Moved! on?
You will find Server Has Moved! on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Server Has Moved! wipe, and how often?
Server Has Moved! wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 25 days 12 hours have passed since this world was made.
What happens on Server Has Moved! when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The latest wipe peaked 0 hours in, with 1 more players queued at that point. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. In the other wipes it slipped under half by day 1.
Player numbers
Where does Server Has Moved! place in the wider field of Rust servers?
Over the last seven days, Server Has Moved! has #15,339 for player hours, in the top 69% of all ranked servers.
Is Server Has Moved! a busy server?
Right now, 0 players are on Server Has Moved!. Over the past seven days, the average player count was 0.
Lists and filters
How should you read the tags on Server Has Moved!?
You'll see Server Has Moved! tagged with gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): 0 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $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): Plugin framework: Carbon in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Server Has Moved! appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Server Has Moved!: 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
What settings and rules apply on Server Has Moved!?
You will find no gather rate in the name of Server Has Moved!. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Server Has Moved! runs which map?
Server Has Moved! runs a game-generated procedural map at size 4,000, seed 2098159377. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
How to join
How do you get onto Server Has Moved!?
Enter client.connect 23.27.211.226:28018 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/koalakopters.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max players0 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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
CarbonPlugin framework: 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 uptime (A+); standing is the one to work on (F).