RUST METRICSFlight deck · live data
Data live Servers11,640 Players39,046 Populated2,948 Fresh wipes 3 h74 Scan5 min
‹ All servers178.44.170.98:28015
Offline Full Queue Fresh wipe Wipe due No query

LocalRustServer1337

Offline 178.44.170.98:28015 checked 30d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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#16,964top 71%
Last wipe30d agono schedule published
Next wipe–no wipe 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 27 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
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe schedule

What wipe timing does LocalRustServer1337 follow?

The rhythm of LocalRustServer1337's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 30 days 16 hours ago the current world was made.

Tag meanings

How should you read the tags on LocalRustServer1337?

Tags published by LocalRustServer1337, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show LocalRustServer1337?

On Rust Metrics, LocalRustServer1337 sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does LocalRustServer1337 sit in the rankings?

Player hours over seven days put LocalRustServer1337 at #16,964, in the top 71% of all ranked servers.

What player count does LocalRustServer1337 carry?

LocalRustServer1337 is not responding; status offline, last seen 30 days 13 hours ago.

Operator and location

What location is LocalRustServer1337 hosted in?

No region comes from LocalRustServer1337. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 178.44.170.98:28015.

What Rust version is LocalRustServer1337 on?

Rust network protocol 2633 and build 165217 on Windows is the build LocalRustServer1337 runs. Matching protocol is required to join. Let Steam update your game.

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

LocalRustServer1337 reports offline. The last reading came 30 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 27 September 2026.

Map and rules

What settings and rules apply on LocalRustServer1337?

No gather rate appears in the name: LocalRustServer1337. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is LocalRustServer1337 on?

Size 4,500 and seed 1337: the game generates the procedural map on LocalRustServer1337 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How do you connect to LocalRustServer1337?

Press F1 in Rust and enter client.connect 178.44.170.98: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 mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.