Rust Data

rustdata.spaceservers64.74.161.162:28017.ipynb

Run all rust-data · live

‹ All servers

Online 64.74.161.162:28015 checked 2h ago

RedlineQc

moddedcarbon

Connect

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

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak 1
rank #10,413 # top 47%
last wipe 10d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123420:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020020:0005:0014:0023:0008:0017: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 Sep5 Oct13 Oct20 Oct28 Oct

Top 47% 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 gap1.5 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 5

The first 48 hours of its last wipes

Sun 18 OctSun 18 OctSat 17 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 Sun 18 Oct, 15:10 UTC10d ago 1 NaN running 0
1 Sun 18 Oct, 03:19 UTC10d ago 1 NaN 0.5 days 0
2 Sat 17 Oct, 20:16 UTC10d ago 1 NaN 0.3 days 0
3 Sat 3 Oct, 01:20 UTC25d ago 1 held half 14.8 days 0
4 Sun 20 Sep, 15:55 UTC38d ago 1 halved by day 5 12.4 days 0
5 Sat 19 Sep, 02:55 UTC39d ago 1 NaN 1.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.

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

Map

3500 · seed 1337
Map of RedlineQc
map
Custom Map
size
3500
seed
1337

Server

srv.info()
address
64.74.161.162:28015
region
–
max players
30
group limit
8, the default
wipe schedule
–
last wipe
18 Oct 2026, 15:10 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
0ShockRust | Blue | NoLimitno group limit · 157 on average205/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 127 on average121/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average183/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average126/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average19/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average50/1000

Quick answers

From the figures on this page.

Population

How does RedlineQc compare in the rankings?

Over the last seven days RedlineQc sits at #10,413 on player hours, in the top 47% of ranked servers.

What population does RedlineQc carry?

RedlineQc reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players and peaked at 1.

Server data

What does performance look like on RedlineQc?

Server fps over the last 48 hours averages 92; the floor is 61. Entity numbers reached 70,456, and that includes buildings, deployables and the rest. The memory field tops out at 3,933 MB. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on RedlineQc?

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

How reliable is RedlineQc, and is it up?

Online is the state at the latest refresh for RedlineQc. The uptime it reports puts the last restart about 5 days 18 hours ago. 168 of 168 hours up over the last 7 full days, or 100%. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is RedlineQc hosted?

For RedlineQc, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 64.74.161.162:28015 is its address.

Settings and map

Which rules apply on RedlineQc, and what settings?

No gather rate appears in the name: RedlineQc. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Anti-cheat status: VAC on.

Which map has RedlineQc selected?

The game generates the map on RedlineQc: procedural, size 3,500, seed 1337. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Custom Map is what the map name field says.

Wipes and dates

When does RedlineQc wipe, and on what schedule?

No next wipe can be predicted for RedlineQc, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 10 days 4 hours ago.

What is wipe day on RedlineQc like?

Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 50% of the time. The drop under half arrived by day 5 in the other cases.

Lists and tags

Which Rust Data filters and lists contain RedlineQc?

The Rust Data lists that RedlineQc fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the server tags on RedlineQc?

These tags are published by RedlineQc and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 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): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 into RedlineQc?

Enter client.connect 64.74.161.162:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/2HCunPdHSE is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Rust survival in its standard form.
mp30
Max players 30 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 Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon Runs on Carbon for plugins.

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 89,289 players 11,829 servers online