On the class lists: F (30), with population over 48 hours and no performance mark.
Players now0/ 20% full
7-day average0peak –
Rank#15,960top 70%
Last wipe14d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 2 on average. Plenty of space to grow.
Standingrank on player hours
30/ 100
F
Working its way up from the back of the class: #15,960 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); 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
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.
No daily history yet.
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOctNov
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 EMC #189 capture (local). Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 97.71.37.190:28015.
How dependable is EMC #189 capture (local), and is it online at the moment?
You cannot join now: EMC #189 capture (local) is offline, last seen 2 days 17 hours ago. It was up 0% of the time over the last 2 full days, 0 of 48 hours. The first sighting by Rust Server Score was on 1 November 2026.
What Rust version is EMC #189 capture (local) on?
You will find EMC #189 capture (local) on Rust network protocol 2634 and build 167781, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does EMC #189 capture (local) wipe, and how often?
There are too few wipes on record for EMC #189 capture (local) to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 14 days 15 hours.
Player numbers
Where does EMC #189 capture (local) sit among Rust servers?
Over the last seven days, EMC #189 capture (local) has #15,960 for player hours, in the top 70% of all ranked servers.
How many players does EMC #189 capture (local) usually have?
It has been 2 days 17 hours since EMC #189 capture (local) was last seen, and it is offline right now. A seven-day average of 0 players applies here.
Lists and filters
What is meant by the tags on EMC #189 capture (local)?
gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): Its slot count is 2; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server are the tags EMC #189 capture (local) publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does EMC #189 capture (local) appear in the Rust Server Score lists and filters?
These Rust Server Score lists count EMC #189 capture (local) among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is EMC #189 capture (local) set up, and what rules does it keep?
Nothing in the name of EMC #189 capture (local) 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. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map EMC #189 capture (local) uses?
A procedural map, generated by the game, is what EMC #189 capture (local) runs.
Connecting
How should you connect to EMC #189 capture (local)?
To connect, start Rust, press F1, and type client.connect 97.71.37.190:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max playersIts slot count is 2.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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); population is the one to work on (F).