RUST METRICSFlight deck · live data
Data live Servers11,808 Players73,203 Populated3,760 Fresh wipes 3 h138 Scan5 min
‹ All servers45.135.228.36:28015
Offline Full Queue Fresh wipe Wipe due No query

EnergyCOREs

Offline 45.135.228.36:28015 checked 14d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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,441top 71%
Last wipe16d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct13 Oct16 Oct19 Oct

Top 71% 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 peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 14:14 UTC16d ago 1 – running 1

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 should you expect from wipe day on EnergyCOREs?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

How often does EnergyCOREs wipe, and when?

To tell the rhythm of EnergyCOREs, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 16 days 7 hours ago the current world was made.

Lists and filters

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

Tags published by EnergyCOREs, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does EnergyCOREs appear in Rust Metrics lists and filters?

On Rust Metrics, EnergyCOREs sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does EnergyCOREs sit in the rankings?

Player hours over seven days put EnergyCOREs at #15,441, in the top 71% of all ranked servers.

What player count does EnergyCOREs carry?

EnergyCOREs is not responding; status offline, last seen 14 days 21 hours ago.

Server

Which location does EnergyCOREs run from?

No region comes from EnergyCOREs. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 45.135.228.36:28015.

What Rust version is EnergyCOREs on?

Rust network protocol 2634 and build 166652 on Windows is the build EnergyCOREs runs. Matching protocol is required to join. Let Steam update your game.

How reliable is EnergyCOREs, and is it online now?

EnergyCOREs reports offline. The last reading came 14 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 4 October 2026.

Rules and settings

What rules does EnergyCOREs enforce, and what are its settings?

Reading the name gives no gather rate for EnergyCOREs. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is EnergyCOREs on?

Procedural map on EnergyCOREs, made by the game's generator.

Join

How do you connect to EnergyCOREs?

Press F1 in Rust and enter client.connect 45.135.228.36:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.