Working its way up from the back of the class: #15,927 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
44/ 100
F
Slipped a little: down 1,788 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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
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 24 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
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 peak0players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
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
Fri 2 Oct, 03:41 UTC27d ago
0
–
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
Which region is 4Netplayers Rust Server probe 1 based in?
4Netplayers Rust Server probe 1 leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 85.14.216.84:21200.
Is 4Netplayers Rust Server probe 1 up, and how steady is its uptime?
The server is down: 4Netplayers Rust Server probe 1 is offline now, with the last sighting 27 days 8 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 24 September 2026.
Which Rust version is 4Netplayers Rust Server probe 1 running?
Rust network protocol 2634 and build 166494 on Linux is what 4Netplayers Rust Server probe 1 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does 4Netplayers Rust Server probe 1 wipe its map?
4Netplayers Rust Server probe 1 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. It has been running its current world for 27 days 8 hours.
What should you expect from wipe day on 4Netplayers Rust Server probe 1?
Across its recent wipes, the busiest moments averaged 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does 4Netplayers Rust Server probe 1 place in the wider field of Rust servers?
Over the last seven days, 4Netplayers Rust Server probe 1 has #15,927 for player hours, in the top 69% of all ranked servers.
How many players does 4Netplayers Rust Server probe 1 usually have?
4Netplayers Rust Server probe 1 is offline at the moment; the last time it was seen was 27 days 8 hours ago.
Lists and filters
What do 4Netplayers Rust Server probe 1's tags stand for?
You'll see 4Netplayers Rust Server probe 1 tagged with gmvanilla (Game mode): You play vanilla survival here; mp10 (Max players): 10 slots are available; 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; cs166494 (Build): The game build is 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. 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 4Netplayers Rust Server probe 1?
Rust Server Score lists that include 4Netplayers Rust Server probe 1: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is 4Netplayers Rust Server probe 1 set up, and what rules does it keep?
The name of 4Netplayers Rust Server probe 1 gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
4Netplayers Rust Server probe 1 runs which map?
4Netplayers Rust Server probe 1 runs a game-generated procedural map at size 4,500, seed 1234567890. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to 4Netplayers Rust Server probe 1?
To connect, start Rust, press F1, and type client.connect 85.14.216.84:21200. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmvanilla,cs166494,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp10
Max players10 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildThe game build is 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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 momentum (F); standing is the one to work on (F).