Loading the evidence…
Preparing your view.
Preparing your view.
Naval support & landing craftActiveProfile in progress
Icebreaker
Japanese icebreaker Shirase (AGB-5003) is a icebreaker originating in Japan.
Shirase (しらせ)
Shirase Glacier
15 March 2007
16 April 2008
20 May 2009
Yokosuka
Hull number: AGB-5003 MMSI number : 431999533 Callsign : JSNJ
Active
Shirase class (1981)
N/A
Icebreaker
Approx. 20,000 tons
138 m (452 ft 9 in)
28 m (91 ft 10 in)
9.2 m (30 ft 2 in)
Diesel-electric Four propulsion motors, 22,000 kW (30,000 hp) (combined) Two shafts; fixed-pitch propellers
19.5 knots (36.1 km/h; 22.4 mph) (maximum) 3 knots (5.6 km/h; 3.5 mph) in 1.5 m (4.9 ft) ice
80 scientists 1,100 tons of cargo
175
3 helicopters
Shirase ( しらせ ) is a Japanese icebreaker operated by the Japan Maritime Self-Defense Force and Japan's fourth icebreaker for Antarctic expeditions .
Reference text from Wikipedia contributors, used under CC BY-SA 4.0.
Japanese icebreaker Shirase (AGB-5003) equipment records. Variants, orders and quantities are shown as reported in each inventory source; coverage is incomplete.
Maritime Self-Defense Force exact named Shirase (capacity 2 AW101 Merlin hel) equipment holdings under LOGISTICS AND SUPPORT, AGBH. Active, operational-reserve and training units excluding equipment in store; November 2025 IISS assessment. This is the named service only, not a national or parent-force total, factory production, ordered future units or combat-readiness measure. Weapons per vessel, crews, payloads and capacity counts are excluded. The exact current AGB5003 individual is bound. The earlier AGB5002 Shirase decommissioned2008 is expressly separate and is not counted.
Reported count for Shirase- class (2008). Service scope: Japan Maritime Self-Defense Force ships; does not replace a national total. 1 distinct quantity component(s) from the same source list; shared rowspan cells counted once. Explicit source inventory scope: active; no other stock status or total inferred. Count column(s): in service: 1. Origin: unstated. The listed variants/roles are the scope, not an immediately deployable count. The components do not establish one inventory census date; the stored date is the retrieved source snapshot.