Online 72.218.192.227:28015 checked 10m ago
Codezalot Rust
Connect
srv = rust.server("72.218.192.227:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 18 Oct. 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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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. 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 1887230747
- map
- Procedural Map
- size
- 3500
- seed
- 1887230747
Server
srv.info()- address
- 72.218.192.227:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 03:21 UTC
- hostname
- –
- first seen
- 18 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 103/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 125/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 97/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 27/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Codezalot Rust rank?
Rank #15,348 on seven-day player hours for Codezalot Rust, within the top 69% of all ranked servers.
How full does Codezalot Rust run?
Current row: 0 players on Codezalot Rust, against 50 slots. Over the last seven days it averaged 0 players.
About the server
How smoothly does Codezalot Rust run?
Averaged over 48 hours: 123 server fps, never under 103. Entity numbers reached 69,099, and that includes buildings, deployables and the rest. Memory peaked at 3,612 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on Codezalot Rust?
The build is Rust network protocol 2634 and build 167781 on Linux, run by Codezalot Rust. Steam updates your game for you, but the protocol must match to join.
Is Codezalot Rust up, and what does its uptime show?
Codezalot Rust reports itself online at the current refresh. The uptime it reports puts the last restart about 10 days 12 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Its earliest recorded date in Rust Data is 18 October 2026.
In which location is Codezalot Rust hosted?
No region is published by Codezalot Rust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 72.218.192.227:28015 is its address.
Map and rules
Which settings and rules does Codezalot Rust run?
No gather rate appears in the name: Codezalot Rust. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Codezalot Rust selected?
Codezalot Rust runs a procedural map of size 3,500 with seed 1887230747, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Codezalot Rust wipe, and on what schedule?
Too few wipes are on record for Codezalot Rust to reveal its rhythm. 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 17 hours ago.
Lists and tags
Which Rust Data filters and lists contain Codezalot Rust?
These Rust Data lists include Codezalot Rust: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on Codezalot Rust hold?
These tags are published by Codezalot Rust and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to Codezalot Rust?
In Rust, F1 opens the console: type client.connect 72.218.192.227:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.