Devblog 240-Meshki
Offline 62.84.33.34:28015 checked 15d ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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. From asking the server directly; low fps and a climbing entity count mean lag.
Li4Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 13 Oct, 14:10 UTC15d ago | 1° | – | running | 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on Devblog 240-Meshki?
At their busiest, its recent wipes averaged 1 players. 0 hours after the latest wipe, the crowd peaked.
What is the wipe schedule on Devblog 240-Meshki?
Devblog 240-Meshki has too few wipes on record yet for its rhythm to show. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 15 days 6 hours ago the server made the world it is on now.
Player counts
How busy is Devblog 240-Meshki?
Devblog 240-Meshki went quiet 15 days 3 hours ago and is offline right now.
How does Devblog 240-Meshki rank against other Rust servers?
Player hours over seven days put Devblog 240-Meshki at #15,327, in the top 71% of ranked servers.
Rules and settings
What are the rules and settings on Devblog 240-Meshki?
The name Devblog 240-Meshki does not specify a gather rate. No group limit is published. The server runs survival, gather, build and raid in the standard game. Combat between players and raiding are both possible. The server browser lists it under Community. The server has VAC, Valve's anti-cheat, turned off.
Server details
Which version of Rust does Devblog 240-Meshki run?
Rust network protocol 2279 on Windows is what Devblog 240-Meshki runs. To join, your game must match the protocol; Steam handles the update.
Is Devblog 240-Meshki online, and how reliable is it?
Last seen 15 days 3 hours ago, Devblog 240-Meshki is offline right now. 0 of 168 hours up over the last 7 full days, which is 0%. The first record of it on Rust Heatmap is 13 October 2026.
Where is Devblog 240-Meshki located?
Nothing about a region comes from Devblog 240-Meshki. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 62.84.33.34:28015 is its address.
Lists and filters
Which Rust Heatmap lists and filters include Devblog 240-Meshki?
Best Rust community servers are the Rust Heatmap lists that Devblog 240-Meshki fits. These are the filters that return it on the list: Type: Community (not modded, not official) and No plugins at all.
What do the server tags on Devblog 240-Meshki mean?
These are the tags Devblog 240-Meshki publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp10 (Max players): The slot count is 10; v2279 (Protocol): To join, run the same version: game protocol 2279; ptrak (Networking): Standard game networking here, which is RakNet; hab366af3 (Custom tag): This is not a standard Rust tag: a plugin or the owner set it; stok (Custom tag): This is not a standard Rust tag: a plugin or the owner set it. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join Devblog 240-Meshki?
To join by console, open it with F1 in Rust and enter client.connect 62.84.33.34:28015. Or press Launch Rust on this page, which connects you through Steam.