Working its way up from the back of the class: #13,624 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
27/ 100
F
Lost ground: down 6,136 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
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 61% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·······
·······
·······
····
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 gap0.8 daysbetween real wipes
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Sat 3 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 17:52 UTC25d ago
2
–
running
0
Fri 2 Oct, 22:52 UTC26d ago
2
–
0.8 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 FortCargo [PvE]. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 164.160.119.229:28015.
How reliable is FortCargo [PvE], and is it up?
You cannot join now: FortCargo [PvE] is offline, last seen 18 days 13 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 2 October 2026.
On what Rust version does FortCargo [PvE] sit?
You will find FortCargo [PvE] on Rust network protocol 2634 and build 166652, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does FortCargo [PvE] reset?
The record holds too few of FortCargo [PvE]'s wipes to tell its 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 26 days 12 hours.
What should you expect from wipe day on FortCargo [PvE]?
The average peak on its recent wipes was 2 players. The crowd on the latest wipe was largest 1 hours after it began.
Player numbers
Where does FortCargo [PvE] sit among Rust servers?
Over the last seven days, FortCargo [PvE] has #13,624 for player hours, in the top 61% of all ranked servers.
What does the population on FortCargo [PvE] look like?
FortCargo [PvE] is offline at the moment; the last time it was seen was 18 days 13 hours ago.
Tags
How should you read the tags on FortCargo [PvE]?
gmhardcore (Game mode): The ruleset is hardcore, the harsher one; mp10 (Max players): The server holds 10 slots; ts0 (Group limit): The team system is turned off; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $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): Carbon provides the plugin framework here are the tags FortCargo [PvE] 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.
Which lists and filters on Rust Server Score show FortCargo [PvE]?
These Rust Server Score lists count FortCargo [PvE] among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Carbon ^y.
Rules and settings
How is FortCargo [PvE] set up, and what rules does it keep?
Nothing in the name of FortCargo [PvE] states a gather rate. No group limit is published. You get hardcore here, Facepunch's most punishing mode. Fighting and raiding between players are both allowed. 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.
FortCargo [PvE] runs which map?
A procedural map, generated by the game, is what FortCargo [PvE] runs.
Getting in
How should you connect to FortCargo [PvE]?
Enter client.connect 164.160.119.229: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 asmp10,ptrak,$r?,v2634,gmhardcore,cs166652,ts0,^z,^y
Game
gmhardcore
Game modeThe ruleset is hardcore, the harsher one.
mp10
Max playersThe server holds 10 slots.
ts0
Group limitThe team system is turned off.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThe game build is 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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
CarbonCarbon provides the plugin framework 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); momentum is the one to work on (F).