Rust Server IndexCard catalogue of Rust servers

Holdings11,733 servers63,580 players197 fresh wipes

Call no.15262 On the shelf · online

US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range

Online 23.160.168.168:28015 checked 10m ago

Subjects 1. modded2. carbon
Players now
0/ 500
0% full
7-day average
0
peak –
Rank
#15,262
top 69%
Last wipeWiped4 OCT2026 · 25d 1h ago
25d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
0123401:0010:0020:0004:0013:0022:00

Hourly average and peak, UTC.

Record sheet B · appended

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Record sheet D · loan terms

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 gap
18.8 daysbetween real wipes
wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

Sun 4 OctWed 16 Sep
01234+0h+9h+19h+28h+38h+47h

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

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
4 OCT 2026Sun 4 Oct, 22:12 UTC25d ago
0 – running 0
16 SEP 2026Wed 16 Sep, 03:48 UTC43d ago
0 – 18.8 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

NA 0/ 10
NA 3/ 100
NA
NA | Apex Aim Arena | 1v1 Facecheck FFA TargetsNA · groups of 8+ · 3 on average
0/ 16
NA 0/ 16
NA2X
The Salt Mines (Official) Solo Only | 2x |NA · groups of 8+ · 2x · monthly · 1 on average
3/ 100
NAMAX
[US] ICEFUSE BATTLEFIELD x1000000000|MYMINI|CLANS|KITS|PVP|FPSNA · groups of 100+ · 1e+09x · weekly · 32 on average
34/ 100
Reference desk

Quick answers

From the figures on this page.

Map and rules

Where can you read the rules and settings that apply on US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range?

You will find no gather rate in the name of US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range. The group limit is 8 players, the game's default. The server runs survival, building, gathering and raiding in the standard game. PvP and raiding are allowed. Plugins or settings change the game; it is listed under Modded in the server browser. Carbon plugins are run on it. The server has VAC, Valve's anti-cheat, turned on.

Tags and filters

On Rust Server Index, which lists and filters carry US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range?

These lists on Rust Server Index take US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range: Modded Rust servers, filed by play style, Aim training servers, filed and North American Rust servers. These filters on the server list bring it up: Region: North America; Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How should you read the tags listed for US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range?

The server's own tags are listed here, and the game's server browser reads them: US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range gives gmrust (Game mode): Survival on standard Rust rules; mp500 (Max players): Player cap: 500; ts8 (Group limit): The team limit is 8, as in the standard game; v2634 (Protocol): Your client must run protocol 2634 to connect; cs166652 (Build): It runs build 166652; ptrak (Networking): The standard RakNet layer carries the connection; $r? (Region code): The region code field is left empty; ^z (Modded): This one is Modded, since plugins or settings change how it plays; ^y (Carbon): Carbon provides the plugin framework. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipes and resets

What should you expect on US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range when wipe day comes?

The average peak across its recent wipes is 0 players. The latest wipe peaked 0 hours in.

When does US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range wipe?

US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range's rhythm cannot be told yet: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. Its present world dates from 25 days 1 hours.

Players and ranking

What position does US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range hold among Rust servers?

On player hours over seven days, US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range takes #15,262, within the top 69% of ranked servers.

Is US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range quiet or crowded?

US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range is currently showing 0 players on 500 slots. Filed under seven-day average: 0 players.

Operator and status

Which Rust build is US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range running?

Rust network protocol 2634 and build 166652 on Linux is what you will find on US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range. The protocol must match before you can join, and Steam takes care of updating it.

What is the uptime and current status of US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range?

Right now US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range is up and running. Uptime for the last 7 full days came to 85%, 143 hours out of 168. On 13 September 2026 it was first seen by Rust Server Index.

Where in the world is US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range hosted?

US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range gives no region tag, so the name is the only pointer, and it points to North America. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 23.160.168.168:28015.

Connecting

What steps lead onto US | Kova's Aimtrain | Facechecks/1v1/Speargun/Range?

Two ways in. Type client.connect 23.160.168.168:28015 into the Rust console after pressing F1, or use Launch Rust and join on this page, which opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

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

Game

gmrust
Game mode Survival on standard Rust rules.
mp500
Max players Player cap: 500.
ts8
Group limit The team limit is 8, as in the standard game.
v2634
Protocol Your client must run protocol 2634 to connect.
cs166652
Build It runs build 166652.
ptrak
Networking The standard RakNet layer carries the connection.
$r?
Region code The region code field is left empty.

Mods and access

^z
Modded This one is Modded, since plugins or settings change how it plays.
^y
Carbon Carbon provides the plugin framework.

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.