Japan · Tier 8 · Tech Tree
Akizuki
Destroyer · 4×2 1 mm
Hit points15 900
Top speed33 kt
Sea detection (base)7.5 km
Turning radius730 m
Overview
General characteristics
NationJapan
ClassDestroyer
Tier8
StatusTech Tree
Hit points15 900
Upgrade slots5
Handling
Mobility
Maximum speed33 kt
Turning radius730 m
Rudder shift time7.8 s
Battle levels8–10
Visibility
Base concealment
Detectability by sea7.5 km
Detectability by air3.6 km
Detectability by submarine3.6 km
Base API profile values before commander skills, upgrades and other modifiers.
Armament
Main battery
Layout4×2 1 mm
Total guns8
Caliber1 mm
Range11.3 km
Reload3 s
180° traverse11.3 s
Maximum dispersion99 m
Rate of fire20/min
AP / SAP shell
AP / SAP shell
Name100 mm AP Type 98
Max damage1 700
Muzzle velocity1 000 m/s
Shell mass13 kg
HE shell
HE shell
Name100 mm HE Type 98
Max damage1 200
Muzzle velocity1 000 m/s
Shell mass13 kg
Fire chance5%
Torpilles
Torpedo armament
Layout1×4 610 mm
Total tubes4
TorpedoType90 mod. 1
Range10 km
Speed62 kt
Reload101 s
Maximum damage17 233
Detectability1.6 km
AA
Anti-aircraft defense
API AA rating55
25 mm · 25 mm/60 Type 96 on a twin mount6 mounts
25 mm · 25 mm/60 Type 96 on a triple mount1 mounts
100 mm · 100 mm/65 Type 98 on a Model A mount4 mounts
ASW
Depth charges
Bombs per drop12
Max damage per bomb4600
Available charges2
Reload40 s
Calculated
Theoretical values
AP broadside alpha13 600
Theoretical AP DPM272 000
HE broadside alpha9 600
Theoretical HE DPM192 000
Theoretical torpedo salvo68 932
Before accuracy, penetration, saturation, angles and other mechanics.
Background
About the ship
Akizuki-class destroyers were designed as air defense ships to escort swift carrier formations. Their main battery was represented by eight 100 mm/65 guns. A total of 13 destroyers of this class were ordered, and 12 were built. After entering service in June 1942, Akizuki participated in the Battle of the Eastern Solomons and the Guadalcanal Campaign, the Battle of the Philippine Sea, and the Battle of Leyte Gulf. The destroyer was sunk during the Battle of Cape Engaño.
Technical data imported from Wargaming’s public API and subject to game updates.