Sizzerver

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 44d ago · 76.130.240.122:28015

Abstract

We describe the public Rust server Sizzerver, reached at 76.130.240.122:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,025 of all servers. It last wiped 48d ago.

Keywordsmodded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/?	no limit published
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,025	no region published
Last wipe	48d ago	no schedule published
Next wipe³	–	no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

This server has not answered a direct query in the last 48 hours.

Figure 2: Server performance. 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.

4Rank

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
No wipe seen yet.

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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 4: The map: Procedural Map.

Table 3: The server's published settings.

Address	`76.130.240.122:28015`
Region	–
Max players	–
Group limit	8, the default
Wipe schedule	–
Last wipe	10 Sep 2026, 04:31 UTC
Hostname	–
First seen	13 Sep 2026
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 157 on average	205/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	121/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average	183/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 90 on average	126/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 87 on average	19/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	50/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of Sizzerver?

There is no region published for Sizzerver. Rust Statistics does not look up the machine's location; it shows where the server says it is. 76.130.240.122:28015 is its address.

A.2What is the reliability of Sizzerver, and is it online?

Right now, Sizzerver is offline, and the last time it was seen was 44 days 1 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. Its first appearance in Rust Statistics's records is 13 September 2026.

A.3What version of Rust is run on Sizzerver?

Rust network protocol 2633 and build 163493 is the version that Sizzerver runs, on Linux. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4On what cycle does Sizzerver wipe?

Too few wipes by Sizzerver have been recorded to determine the pattern. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 48 days 13 hours.

Player count

A.5What position does Sizzerver occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Sizzerver at #15,025, within the top – of ranked servers.

A.6At what level does Sizzerver operate in terms of players?

The last recorded sighting of Sizzerver was 44 days 1 hours ago; it is offline now.

Tags, lists

A.7How should the tags on Sizzerver be interpreted?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp0 (Max players): The slot count is 0; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): Joining requires the same game version: protocol 2633; cs163493 (Build): Build 163493 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): The plugin framework is Carbon, which Sizzerver publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can Sizzerver be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Sizzerver: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Settings and map

A.9Which settings and rules are in force on Sizzerver?

The name of Sizzerver states no gather rate. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. The plugin count is Carbon. The server has VAC on, Valve's anti-cheat.

A.10What is the map for Sizzerver?

A procedural map, generated by the game, is what Sizzerver runs.

How to join

A.11How do you connect to Sizzerver?

Enter client.connect 76.130.240.122:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp0,ptrak,$r?,v2633,gmrust,cs163493,ts8,^z,^y.

Table 5: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Rust survival, in its standard form.
`mp0`	Max players. The slot count is 0.
`ts8`	Group limit. Teams are limited to 8, as the game defaults.
`v2633`	Protocol. Joining requires the same game version: protocol 2633.
`cs163493`	Build. Build 163493 is the one running.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. A region code has not been set.
Mods and access
`^z`	Modded. The game is altered by plugins or settings, so it is listed as Modded.
`^y`	Carbon. The plugin framework is 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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.