Working its way up from the back of the class: #15,491 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
51/ 100
D
Moving up: up 359 places this week.
A term to build on.
Strongest in momentum (D); 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.
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 69% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
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
Come on let's go! leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 144.76.28.124:45625.
How dependable is Come on let's go!, and is it online at the moment?
You cannot join now: Come on let's go! is offline, last seen 42 days 3 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 17 September 2026.
Which Rust version is Come on let's go! running?
Rust network protocol 2633 and build 163794 on Linux is what Come on let's go! runs. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Come on let's go! wipe, and how often?
The record holds too few of Come on let's go!'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 42 days 5 hours.
Population
What position does Come on let's go! hold in the rankings?
In the top 69% of all ranked servers, Come on let's go! sits at #15,491 for player hours over the last seven days.
Is Come on let's go! a busy server?
The last sighting of Come on let's go! was 42 days 3 hours ago, and it is offline right now.
Lists and filters
What do Come on let's go!'s tags stand for?
The game's browser takes its cue from the tags Come on let's go! has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): 40 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. 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 Rust Server Score filters and lists feature Come on let's go!?
These Rust Server Score lists count Come on let's go! among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
How is Come on let's go! set up, and what rules does it keep?
You will find no gather rate in the name of Come on let's go!. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on Come on let's go!?
Come on let's go! runs a procedural map, which the game generates.
How to join
How do you get onto Come on let's go!?
Enter client.connect 144.76.28.124:45625 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 asmp40,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max players40 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$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 momentum (D); standing is the one to work on (F).