Working its way up from the back of the class: #6,894 on player hours.
Uptimehours on the list, last 48
12/ 100
F
Attendance needs work: on the list only 6 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 (C+); 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.
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 31% 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 peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 14:22 UTC2d ago
2
–
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
Rust in Pieces leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 84.29.211.178:28015.
How dependable is Rust in Pieces, and is it online at the moment?
You cannot join now: Rust in Pieces is offline, last seen 23 hours ago. For the last 1 full day, it was up 6 of 24 hours, or 25% of the time. It was first seen by Rust Server Score on 25 October 2026.
Which Rust version is Rust in Pieces running?
Rust network protocol 2635 and build 168909 on Windows is what Rust in Pieces runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does Rust in Pieces wipe, and how often?
Rust in Pieces 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. 2 days 7 hours have passed since this world was made.
What happens on Rust in Pieces when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
What position does Rust in Pieces hold in the rankings?
In the top 31% of all ranked servers, Rust in Pieces sits at #6,894 for player hours over the last seven days.
Is Rust in Pieces a busy server?
It has been 23 hours since Rust in Pieces was last seen, and it is offline right now. The seven-day average is 1 players, with a peak of 2. The highest average in the last 48 hours came at 14:00 UTC, with 1 players.
Tags and filters
How should you read the tags on Rust in Pieces?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp0 (Max players): Its slot count is 0; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^p (PvE): Players do not fight one another here; the world is the danger are the tags Rust in Pieces 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 Rust in Pieces?
These Rust Server Score lists count Rust in Pieces among them: Best community servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 3 days.
Server rules
How is Rust in Pieces set up, and what rules does it keep?
The name of Rust in Pieces gives no gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on Rust in Pieces?
A procedural map, generated by the game, is what Rust in Pieces runs.
Getting in
What is the way to join Rust in Pieces?
Enter client.connect 84.29.211.178: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 asmp0,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp0
Max playersIts slot count is 0.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
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 (C+); uptime is the one to work on (F).