RUST METRICSFlight deck · live data
Data live Servers11,875 Players95,389 Populated3,882 Fresh wipes 3 h387 Scan5 min
‹ All servers163.44.114.111:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_27843

Offline 163.44.114.111:28015 checked 27d ago

COM 1 · connect

Server instruments

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

Players now

2% 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#13,819top 60%
Last wipe27d 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 2 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 60% 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

Reset cycle

What wipe timing does RustServer_27843 follow?

The rhythm of RustServer_27843'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. The world in play was created 27 days 12 hours ago.

Lists and filters

How should you read the tags on RustServer_27843?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): Game build reading: 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from RustServer_27843. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_27843 appear in Rust Metrics lists and filters?

On Rust Metrics, RustServer_27843 sits in these lists: 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; Group limit: 5 or more.

Player count

Where does RustServer_27843 sit in the rankings?

Ranking for RustServer_27843: #13,819 on seven-day player hours, top 60% of all ranked servers.

What is the population on RustServer_27843?

RustServer_27843 is not responding; status offline, last seen 27 days 10 hours ago.

Server

Where does RustServer_27843 sit?

No region tag on RustServer_27843. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 163.44.114.111:28015.

What Rust version is RustServer_27843 on?

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

How reliable is RustServer_27843, and is it online now?

RustServer_27843 reports offline. The last reading came 27 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 2 October 2026.

Map and rules

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

No gather rate appears in the name: RustServer_27843. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on RustServer_27843?

Size 3,000 and seed 3288: the game generates the procedural map on RustServer_27843 from them. 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 RustServer_27843?

Press F1 in Rust and enter client.connect 163.44.114.111: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 mp50,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build Game build reading: 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.