Rust Data

rustdata.spaceservers185.180.2.44:27685.ipynb

Run all rust-data · live

‹ All servers

Online 185.180.2.44:28685 checked 12m ago

VeecaMC-Private

teams off moddedoxidehardcore

Connect

srv = rust.server("185.180.2.44:27685")
print(srv.connect_command)

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak 3
rank #7,089 # top 32%
last wipe 3d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5201:0010:0019:0004:0013:0023:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510001:0010:0019:0004:0013:0023: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

usual gap4.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held67%else halves by day 1

The first 48 hours of its last wipes

Sun 25 OctWed 21 OctSun 11 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 25 Oct, 15:32 UTC3d ago 2 NaN running 0
1 Wed 21 Oct, 17:01 UTC7d ago 2 held half 3.9 days 2
2 Sun 11 Oct, 14:35 UTC17d ago 2 held half 10.1 days 0
3 Tue 6 Oct, 16:30 UTC22d ago 1 halved by day 1 4.9 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.

display(srv.map, srv.info())

Map

4000 · seed 0
Custom map, no picture published
map
Custom Map
size
4000
seed
–

Server

srv.info()
address
185.180.2.44:28685
region
–
max players
30
group limit
teams off
wipe schedule
–
last wipe
25 Oct 2026, 15:32 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0TheLastOfRust Hardcore PvE Zombie Survivalno group limit · 7 on average6/100
1Nikki & Yuni Hardcore Solo/Duo | Wiped 10/15 | No Tech Tree | RNA · no group limit · biweekly · 3 on average5/50
2Alone & AfraidOC · no group limit · biweekly · 2 on average1/50
3[BR/LATAM] Evolution PVE | Hardcore Zombie SurvivalSA · groups of 15+ · biweekly · 2 on average2/50
4TheLastOfRust Premium Hardcore PvE Zombie Survivalno group limit · 2 on average3/100
5ShockRust | Blue | NoLimitno group limit · 155 on average36/500

Quick answers

From the figures on this page.

Population

How does VeecaMC-Private compare in the rankings?

Over the last seven days VeecaMC-Private sits at #7,089 on player hours, in the top 32% of ranked servers.

What population does VeecaMC-Private carry?

Current row: 0 players on VeecaMC-Private, against 30 slots. Over the last seven days it averaged 0 players and peaked at 3. Averaged by hour over 48 hours, 08:00 UTC is the busiest, at 1 players.

Server facts

How smoothly does VeecaMC-Private run?

Averaged over 48 hours: 22 server fps, never under 19. Buildings, deployables and all else in the world took the count as high as 100,733 entities. A high of 3,372 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does VeecaMC-Private run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by VeecaMC-Private. The protocol has to match before you can join, and Steam does the updating.

How reliable is VeecaMC-Private, and is it up?

VeecaMC-Private reports itself online at the current refresh. Count back 18 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.

In which location is VeecaMC-Private hosted?

For VeecaMC-Private, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.180.2.44:28685.

Rules, settings, map

Which settings and rules does VeecaMC-Private run?

The name VeecaMC-Private carries no gather rate. Group limits do not appear in its data. Game mode hardcore, with this note: Facepunch at its most unforgiving. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has VeecaMC-Private selected?

Generated by the game at size 4,000, the map on VeecaMC-Private is procedural. Under map name you will find: Custom Map.

Wipes and dates

On what schedule does VeecaMC-Private wipe?

No next wipe can be predicted for VeecaMC-Private, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 3 days 9 hours ago.

On VeecaMC-Private, what happens on wipe day?

Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 17 hours in. Half the peak or more was held to the next wipe in 67% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags and filters

Where does VeecaMC-Private appear among Rust Data lists and filters?

These Rust Data lists include VeecaMC-Private: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last week.

How should you read the server tags on VeecaMC-Private?

Read by the game's server browser, the tags VeecaMC-Private publishes are: gmhardcore (Game mode): Hardcore ruleset, the harsher one; mp30 (Max players): Slot count: 30; ts0 (Group limit): The team system is off; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join VeecaMC-Private?

In Rust, F1 opens the console: type client.connect 185.180.2.44:28685. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp30,ptrak,$r?,v2635,gmhardcore,cs168909,ts0,^o^z

Game

gmhardcore
Game mode Hardcore ruleset, the harsher one.
mp30
Max players Slot count: 30.
ts0
Group limit The team system is off.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the 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.

Rust Data 45,091 players 11,692 servers online