Rust Data

rustdata.spaceservers64.223.131.132:28017.ipynb

Run all rust-data · live

‹ All servers

Online 64.223.131.132:28015 checked 10m ago

EZLogik Build Home (dev)

moddedcarbon

Connect

srv = rust.server("64.223.131.132:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 1
rank #11,444 # top 51%
last wipe 19d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75108:0017:0002:0011:0021:0006:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k26 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 51% 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 gap2.8 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 9 OctSat 3 OctThu 1 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, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 9 Oct, 12:49 UTC19d ago 1 NaN running 1
1 Sat 3 Oct, 23:55 UTC25d ago 0 NaN 5.5 days 0
2 Thu 1 Oct, 03:48 UTC28d ago 1 halved by day 1 2.8 days 0
3 Wed 30 Sep, 20:41 UTC28d ago 1 NaN 0.3 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.

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

Map

Custom map, no picture published
map
Custom Map
size
–
seed
–

Server

srv.info()
address
64.223.131.132:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
9 Oct 2026, 12:49 UTC
hostname
–
first seen
26 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |EU · groups of 8+ · 116 on average64/999
1[NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames |NA · groups of 8+ · 91 on average69/999
2[AU] Rusticated.com - Creative Sandbox | Build | Never WipesOC · groups of 8+ · 52 on average96/150
3Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFAEU · groups of 30+ · weekly · 37 on average1/100
4AQRUX RUST BUILD | CREATIVE | SANDBOXEU · groups of 8+ · monthly · 24 on average22/100
5KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfightgroups of 8+ · 23 on average14/100

Quick answers

From the figures on this page.

Population data

What position does EZLogik Build Home (dev) take in the server rankings?

Over the last seven days EZLogik Build Home (dev) sits at #11,444 on player hours, in the top 51% of ranked servers.

What population does EZLogik Build Home (dev) carry?

EZLogik Build Home (dev) reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 01:00 UTC is the busiest, at 1 players.

Server facts

What is the Rust version on EZLogik Build Home (dev)?

Rust network protocol 2635 and build 168909 on Linux is what EZLogik Build Home (dev) runs. Steam updates your game for you, but the protocol must match to join.

Is EZLogik Build Home (dev) up, and what does its uptime show?

Online is the state at the latest refresh for EZLogik Build Home (dev). Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 26 September 2026.

In which location is EZLogik Build Home (dev) hosted?

For EZLogik Build Home (dev), no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 64.223.131.132:28015.

Rules, settings, map

Which settings and rules does EZLogik Build Home (dev) run?

You will not find a gather rate in the string EZLogik Build Home (dev). Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.

Wipe schedule

When does EZLogik Build Home (dev) wipe, and on what schedule?

Irregular wipe times on EZLogik Build Home (dev) leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 19 days 19 hours ago.

On EZLogik Build Home (dev), what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 1.

Tags and filters

Which lists on Rust Data hold EZLogik Build Home (dev), and which filters?

On Rust Data, EZLogik Build Home (dev) appears in these lists: Modded Rust servers and Servers with build or creative tags. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How should you read the server tags on EZLogik Build Home (dev)?

The game's server browser reads these tags from EZLogik Build Home (dev): gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join EZLogik Build Home (dev)?

Enter client.connect 64.223.131.132:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon Plugin framework: Carbon.

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 41,406 players 11,624 servers online