Working its way up from the back of the class: #15,330 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
15/ 100
F
Lost ground: down 10,751 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.
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 19 Sep. 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
2 wipe days in the last 16 weeks
MTWTFSS
···W···
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····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
Sat 10 OctThu 16 Jul
Players each hour, from the hour of the wipe. The latest peaked at 2, 31 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 22:58 UTC19d ago
2
–
running
1
Thu 16 Jul, 09:14 UTC105d ago
–
–
86.6 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 core_main. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 107.13.210.75:28015 is the address to use.
How dependable is core_main, and is it online at the moment?
You cannot join now: core_main is offline, last seen 11 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 19 September 2026, Rust Server Score saw it for the first time.
What Rust version is core_main on?
Rust network protocol 2223 on Windows is what core_main runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does core_main wipe, and how often?
There are too few wipes on record for core_main to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 105 days 14 hours.
What happens on core_main when wipe day arrives?
Recent wipes have peaked at 2 players on average. 31 hours after the latest wipe began, the crowd hit its peak.
Population
What position does core_main hold in the rankings?
Over the last seven days, core_main has #15,330 for player hours, in the top 70% of all ranked servers.
What does the population on core_main look like?
core_main is offline at the moment; the last time it was seen was 11 days 23 hours ago.
Tags
What is meant by the tags on core_main?
You'll see core_main tagged with gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; v2223 (Protocol): To get in, your game needs to be on the same version: the protocol is 2223; ptrak (Networking): RakNet handles it, the game's default network layer; hd9562fd7 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner; stok (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature core_main?
These Rust Server Score lists count core_main 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.
Map and rules
Which rules does core_main enforce, and what are its settings?
The name of core_main gives no gather rate. It publishes no limit on group size. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
core_main runs which map?
core_main runs a game-generated procedural map at size 4,500, seed 87583452. 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 core_main?
Enter client.connect 107.13.210.75: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 asmp50,ptrak,v2223,hd9562fd7,stok,gmrust
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
v2223
ProtocolTo get in, your game needs to be on the same version: the protocol is 2223.
ptrak
NetworkingRakNet handles it, the game's default network layer.
Other
hd9562fd7
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
stok
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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).