Rust PopulationField survey · Rust servers
Observing 39,471 players 11,695 servers 2,990 with someone on 89 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 7,185habitat unknownfirst seen 13 Sep 2026

10.145.64.33

Offline 31.134.188.77:28015 checked 2d ago

Measurements

Players now
0/ 1
0% full
7-day average
1
peak 1
Rank
#7,185
top 32%
Last wipe
6d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

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.

Obs. 3 · standing

Rank

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

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

Obs. 4 · the wipe cycle

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

6.3 days
usual gap
between real wipes
0%
on rhythm
of its recent wipes
1
wipe-day peak
players, last three wipes
100%
crowd held
of its cycles kept half the crowd

The first 48 hours of its last wipes

Thu 22 OctSat 17 OctTue 13 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 22:20 UTC6d ago 1 – running 0
Sat 17 Oct, 23:51 UTC11d ago 1 held half 4.9 days 0
Tue 13 Oct, 12:23 UTC15d ago 0 – 4.5 days 0
Mon 5 Oct, 18:43 UTC23d ago 0 – 7.7 days 1
Sat 26 Sep, 21:23 UTC32d ago 1 – 8.9 days 1

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.

Field questions

Quick answers

from the figures on this page

Player counts

How does 10.145.64.33 rank against other Rust servers?

By player hours over the last seven days, 10.145.64.33 places at #7,185, within the top 32% of ranked servers.

How busy is 10.145.64.33?

At this count 10.145.64.33 is offline, with its last sighting 2 days ago. Averaged over seven days, it drew 1 players and reached a peak of 1.

Tags

What do the server tags on 10.145.64.33 mean?

The game's server browser reads the tags 10.145.64.33 publishes: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): You can join up to 1 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): No region code is set. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include 10.145.64.33?

On Rust Population, 10.145.64.33 is filed under these lists: Community servers, field-listed. Look for it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Wipe notes

What does wipe day look like on 10.145.64.33?

The busiest point of its recent wipes averaged 1 players. 17 hours after the latest wipe the crowd peaked. Half that peak held until the next wipe in 100% of its recent wipes.

What is the wipe schedule on 10.145.64.33?

Irregular times are when 10.145.64.33 wipes, which leaves no next wipe to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 6 days 3 hours ago.

Settings

Which map does 10.145.64.33 run?

The map on 10.145.64.33 is procedural, made by the game.

What are the rules and settings on 10.145.64.33?

The name tells you nothing about gather rates: 10.145.64.33 states none. Eight players per group is the default, and it applies here. survival is what it runs, raid, build and gather: the standard game. Combat between players, raids included, is permitted. You will find it under Community: it is a community server. The anti-cheat VAC from Valve is disabled.

About the server

Which version of Rust does 10.145.64.33 run?

Rust network protocol 2635 and build 168909 on Windows is what 10.145.64.33 uses. The protocol must match for you to join, and Steam updates it for you.

Is 10.145.64.33 online, and how reliable is it?

Currently offline, 10.145.64.33 was last seen 2 days ago. It was up 17% of the time over the last 7 full days, 29 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.

Where is 10.145.64.33 located?

No region is published by 10.145.64.33. The location a server claims is what Rust Population shows, not the place where the machine stands. 31.134.188.77:28015 is where it lives.

How to join

How do I join 10.145.64.33?

Open the console with F1 in Rust and enter client.connect 31.134.188.77:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players You can join up to 1 slots.
ts8
Group limit 8 per team is the default limit.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The standard network layer, RakNet, is in use.
$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.