Working its way up from the back of the class: #15,886 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
50/ 100
D
Holding steady: up 84 places this week.
A term to build on.
Strongest in momentum (D); wipes are the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·W·····
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap10.2 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 6
The first 48 hours of its last wipes
Tue 29 SepSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 29 Sep, 21:23 UTC29d ago
1
–
running
0
Sat 19 Sep, 16:56 UTC40d ago
2
halved by day 6
10.2 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Day After Tomorrow Zombie leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 141.95.34.176:25783.
Is Day After Tomorrow Zombie up, and how steady is its uptime?
The server is down: Day After Tomorrow Zombie is offline now, with the last sighting 21 days 9 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is Day After Tomorrow Zombie running?
You will find Day After Tomorrow Zombie on Rust network protocol 2633 and build 165217, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does Day After Tomorrow Zombie wipe, and how often?
There are too few wipes on record for Day After Tomorrow Zombie to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 29 days 23 hours have passed since this world was made.
What happens on Day After Tomorrow Zombie when wipe day arrives?
The average peak on its recent wipes was 2 players. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 6.
Player count
What position does Day After Tomorrow Zombie hold in the rankings?
In the top 72% of all ranked servers, Day After Tomorrow Zombie sits at #15,886 for player hours over the last seven days.
How many players does Day After Tomorrow Zombie usually have?
The last sighting of Day After Tomorrow Zombie was 21 days 9 hours ago, and it is offline right now.
Tags
What do Day After Tomorrow Zombie's tags stand for?
The game's browser takes its cue from the tags Day After Tomorrow Zombie has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Day After Tomorrow Zombie appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Day After Tomorrow Zombie among them: Modded Rust servers, graded and Rust zombie servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
What settings and rules apply on Day After Tomorrow Zombie?
The name of Day After Tomorrow Zombie gives no gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Day After Tomorrow Zombie runs which map?
The game generates the procedural map on Day After Tomorrow Zombie at size 4,000 with seed 1996107046. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto Day After Tomorrow Zombie?
Enter client.connect 141.95.34.176:25783 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs165217,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.
A term to build on. Strongest in momentum (D); wipes are the one to work on (F).