A quiet classroom so far: 1 of 8 on average. Plenty of space to grow.
Standingrank on player hours
46/ 100
D
Working its way up from the back of the class: #11,942 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); uptime 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
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
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 54% 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, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 11:01 UTC19d 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
You'll find no region listed by Matt's Rust Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 77.97.55.4:28015.
How reliable is Matt's Rust Server, and is it up?
At this moment, Matt's Rust Server is offline; the last time it was seen was 31 hours ago. For the last 7 full days, it was up 2 of 168 hours, or 1% of the time. The first sighting by Rust Server Score was on 8 October 2026.
On what Rust version does Matt's Rust Server sit?
Rust network protocol 2635 and build 168909 on Windows is what Matt's Rust Server runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Matt's Rust Server wipe its map?
Matt's Rust Server has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 19 days 12 hours have passed since this world was made.
What happens on Matt's Rust Server when wipe day arrives?
The average peak on its recent wipes was 1 players. Peak numbers came 2 hours into the latest wipe.
Population
Where does Matt's Rust Server sit among Rust servers?
In the top 54% of all ranked servers, Matt's Rust Server sits at #11,942 for player hours over the last seven days.
What does the population on Matt's Rust Server look like?
It has been 31 hours since Matt's Rust Server was last seen, and it is offline right now. The seven-day average is 1 players, with a peak of 1. The highest average in the last 48 hours came at 16:00 UTC, with 1 players.
Lists and filters
How should you read the tags on Matt's Rust Server?
The game's browser takes its cue from the tags Matt's Rust Server has set: gmrust (Game mode): Rust survival, played by the standard rules; mp8 (Max players): 8 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; 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): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. 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 Matt's Rust Server?
These Rust Server Score lists count Matt's Rust Server among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on Matt's Rust Server?
Nothing in the name of Matt's Rust Server states a 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. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. You are covered by VAC, Valve's anti-cheat.
Matt's Rust Server runs which map?
Matt's Rust Server runs a game-generated procedural map at size 2,000, seed 1977670499. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to Matt's Rust Server?
To connect, start Rust, press F1, and type client.connect 77.97.55.4:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp8
Max players8 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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 (D); uptime is the one to work on (F).