RUST METRICSFlight deck · live data
Data live Servers11,665 Players33,246 Populated2,811 Fresh wipes 3 h81 Scan5 min
‹ All servers107.13.210.75:28015
Offline Full Queue Fresh wipe Wipe due No query

core_main

Offline 107.13.210.75:28015 checked 11d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,330top 70%
Last wipe104d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep14 Oct19 Oct24 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

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
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 31 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 22:58 UTC18d ago 2 – running 1
Thu 16 Jul, 09:14 UTC104d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on core_main when wipe day comes?

The busiest point of its recent wipes drew 2 players on average. 31 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does core_main follow?

To tell the rhythm of core_main, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 104 days 18 hours ago.

Lists and filters

Which tags does core_main carry, and what do they mean?

These are the tags core_main publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; v2223 (Protocol): Match the game version: protocol 2223 is required; ptrak (Networking): This is RakNet, Rust's usual network layer; hd9562fd7 (Custom tag): A plugin or the owner set this tag; Rust does not ship it; stok (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show core_main?

These Rust Metrics lists carry core_main: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all.

Player count

Where does core_main sit in the rankings?

Player hours over seven days put core_main at #15,330, in the top 70% of all ranked servers.

What is the population on core_main?

Reading for core_main: offline at this moment; last seen 11 days 3 hours ago.

Operator and location

What location is core_main hosted in?

No region comes from core_main. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 107.13.210.75:28015.

What Rust version is core_main on?

Rust network protocol 2223 on Windows is the build core_main runs. To get in, your game needs the same protocol; Steam applies the update.

Is core_main up, and how often does it stay up?

Reading: offline. core_main last answered 11 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 September 2026.

Settings and map

What settings and rules apply on core_main?

No gather rate appears in the name: core_main. The group limit is not published. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on core_main?

Check: map. Procedural, size 4,500, seed 87583452, generated by the game on core_main. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Join

What do you do to join core_main?

Check: join. Open Rust, press F1, then enter client.connect 107.13.210.75:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,v2223,hd9562fd7,stok,gmrust

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
v2223
Protocol Match the game version: protocol 2223 is required.
ptrak
Networking This is RakNet, Rust's usual network layer.

Other

hd9562fd7
Custom tag A plugin or the owner set this tag; Rust does not ship it.
stok
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.