Working its way up from the back of the class: #15,918 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
16/ 100
F
Lost ground: down 10,779 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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.
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.
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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
···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.
usual gap5 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3
The first 48 hours of its last wipes
Thu 8 OctSat 3 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 00:43 UTC21d ago
0
–
running
0
Sat 3 Oct, 01:06 UTC26d ago
2
halved by day 3
5 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 RustServer_20354. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 163.44.101.87:28015 is the address to use.
How dependable is RustServer_20354, and is it online at the moment?
You cannot join now: RustServer_20354 is offline, last seen 21 days 9 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does RustServer_20354 sit?
Rust network protocol 2597 and build 130842 on Linux is what RustServer_20354 runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does RustServer_20354 wipe its map?
RustServer_20354 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 21 days 10 hours have passed since this world was made.
What happens on RustServer_20354 when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 3.
Player count
Where does RustServer_20354 sit among Rust servers?
In the top 72% of all ranked servers, RustServer_20354 sits at #15,918 for player hours over the last seven days.
What does the population on RustServer_20354 look like?
The last sighting of RustServer_20354 was 21 days 9 hours ago, and it is offline right now.
Lists and filters
What is meant by the tags on RustServer_20354?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2597 (Protocol): Join only if your game runs protocol 2597; cs130842 (Build): This runs on build 130842; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags RustServer_20354 publishes, and the game's server browser reads them. 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 Rust Server Score filters and lists feature RustServer_20354?
Rust Server Score lists that include RustServer_20354: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is RustServer_20354 set up, and what rules does it keep?
The name of RustServer_20354 gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
RustServer_20354 runs which map?
A procedural map of size 4,500 and seed 646863724, generated by the game, is what RustServer_20354 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to RustServer_20354?
Enter client.connect 163.44.101.87: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?,v2597,gmrust,cs130842,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2597
ProtocolJoin only if your game runs protocol 2597.
cs130842
BuildThis runs on build 130842.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set 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. Strongest in standing (F); wipes are the one to work on (F).