RUST METRICSFlight deck · live data
Data live Servers11,631 Players45,053 Populated3,098 Fresh wipes 3 h93 Scan5 min
‹ All servers5.83.140.205:26487
Online Full Queue Fresh wipe Wipe due No query

K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT

Online 5.83.140.205:26487 checked 7m ago

1000x moddedoxide
COM 1 · connect

Server instruments

last reading Wed 06:00 UTC
0 10 20 30 40 PAX 0 /40

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 137 SERVER FPS

Server fps

48 h low 36 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 68,257 ×1000

Entities

48 h range 65,815–68,390 · memory 4,096 MB
1239 ET SINCE RESTART 4D 21H

Uptime

4 days 21 hours since its last restart, at the last reading
7-day average0peak 1
Rank#11,127top 50%
Last wipe4d agono schedule published
Next wipe–too few wipes seen yet
Memory4,096MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75109:0018:0003:0012:0021:0006:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040009:0018:0003:0012:0021:0006:00

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 14 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
15k10k15k20k14 Oct17 Oct20 Oct22 Oct25 Oct28 Oct

Top 50% 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 gap5.5 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Fri 23 OctSat 17 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 09:01 UTC4d ago 1 – running 0
Sat 17 Oct, 20:15 UTC10d ago 3 halved by day 2 5.5 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

Wipe timing

What should you expect from wipe day on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT?

The busiest point of its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 34 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2 it fell below half when it didn't.

How often does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT wipe, and when?

Its rhythm cannot be told from the wipes of K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 4 days 23 hours ago the current world was made.

Tag meanings

How should you read the tags on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT?

These are the tags K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp40 (Max players): Slots: 40; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT appear in Rust Metrics lists and filters?

Rust Metrics lists featuring K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT: Gather rate above 10x: server list and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: More than 10x.

Occupancy

What position does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT hold among Rust servers?

Ranking for K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT: #11,127 on seven-day player hours, top 50% of all ranked servers.

What player count does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT carry?

0 of 40 slots are filled on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT right now. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 20:00 UTC, averaging 1 players at that hour.

Server details

Where does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT sit?

No region tag on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 5.83.140.205:26487.

What Rust version is K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT on?

Reading: K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT perform?

Reading: 159 server fps on average across the last 48 hours. It never dropped below 36. Reading: 68,390 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,739 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT, and is it online?

K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 4 days 21 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. The first sighting on Rust Metrics was 14 October 2026.

Map and rules

What rules does K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT enforce, and what are its settings?

Gather rate check: 1000x. That comes from the name K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT?

From seed 1337, the game generates the procedural map on K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT. Its size is 3,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

How can you get onto K-13 NUMBER 1 | X1000 | MAX PvP | NO LIMIT?

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

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp40
Max players Slots: 40.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.