RUST METRICSFlight deck · live data
Data live Servers11,800 Players69,961 Populated3,675 Fresh wipes 3 h123 Scan5 min
‹ All servers188.245.7.13:28015
Offline Full Queue Fresh wipe Wipe due No query

Swerver

Offline 188.245.7.13:28015 checked 16d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,483top 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, measured since 12 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k8 Oct10 Oct12 Oct15 Oct17 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.

usual gap0.3 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 12 OctMon 12 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 09:25 UTC16d ago 0 – running 0
Mon 12 Oct, 02:36 UTC16d ago 0 – 0.3 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 should you expect from wipe day on Swerver?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Swerver wipe, and when?

To tell the rhythm of Swerver, 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 it runs now was made 16 days 11 hours ago.

Lists and filters

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

Tags published by Swerver, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): The server runs game build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Swerver appear in Rust Metrics lists and filters?

On Rust Metrics, Swerver sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does Swerver hold among Rust servers?

Ranking for Swerver: #15,483 on seven-day player hours, top 71% of all ranked servers.

How full does Swerver get?

Status for Swerver: offline. Last seen 16 days 2 hours ago.

Server

Where does Swerver sit?

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

What Rust version is Swerver on?

Version check: Rust network protocol 2634 and build 167584 on Linux, run by Swerver. Matching protocol is required to join. Let Steam update your game.

How reliable is Swerver, and is it online now?

Check: connection. Swerver is offline at this moment. Last contact was 16 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 8 October 2026.

Settings and map

What settings and rules apply on Swerver?

No gather rate appears in the name: Swerver. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Swerver on?

Check: map. Procedural, size 1,000, seed 456456456, generated by the game on Swerver. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto Swerver?

To join: start Rust, press F1 and type client.connect 188.245.7.13:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build The server runs game build 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.