2023 Pacific typhoon season

2023 Pacific typhoon season

First system formed	March 4, 2023
Last system dissipated	Season ongoing
Strongest storm1	Mawar – 900 hPa (mbar), 215 km/h (130 mph) (10-minute sustained)
Total depressions	24
Total storms	13
Typhoons	8
Super typhoons	3 (unofficial)
Total fatalities	167 total
Total damage	$16 billion (2023 USD)
1Strongest storm is determined by lowest pressure
Pacific typhoon seasons 2021, 2022, 2023, 2024, 2025

The 2023 Pacific typhoon season is an ongoing event in the annual cycle of tropical cyclone formation, in which tropical cyclones form in the western Pacific Ocean. The season runs throughout 2023, though most tropical cyclones typically develop between May and October. The season's first named storm, Sanvu, developed on April 21. The following month, Mawar, intensified into the first typhoon of the season on May 21, becoming one of the strongest Northern Hemisphere tropical cyclones on record in May, and the second-strongest early-season tropical cyclone, behind only Surigae in April 2021. An exceptionally notable storm was Typhoon Doksuri in mid-late July, which devastated the northern Philippines, Taiwan and China, causing $15.4 billion in damage, as well as becoming the costliest typhoon to hit Mainland China.

The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and 180th meridian. Within the northwestern Pacific Ocean, there are two separate agencies that assign names to tropical cyclones which can often result in a cyclone having two names. The Japan Meteorological Agency (JMA) will name a tropical cyclone if it has 10-minute sustained wind speeds of at least 65 km/h (40 mph) anywhere in the basin. The Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assigns names to tropical cyclones which move into or form as a tropical depression in the Philippine Area of Responsibility (PAR), located between 135°E and 115°E and between 5°N–25°N, regardless of whether or not a tropical cyclone has already been given a name by the JMA. Tropical depressions that are monitored by the United States' Joint Typhoon Warning Center (JTWC) are given a number with a "W" suffix.

Seasonal forecasts

TSR forecasts Date	Tropical storms	Total Typhoons	Intense TCs	ACE	Ref.
Average (1965–2022)	25.7	16.1	8.7	290
May 5, 2023	29	19	13	394
July 7, 2023	29	19	12	382
August 8, 2023	29	20	14	393
Other forecasts Date	Forecast Center	Period		Systems	Ref.
January 13, 2023	PAGASA	January–March		0–2 tropical cyclones
January 13, 2023	PAGASA	April–June		2–4 tropical cyclones
June 27, 2023	PAGASA	July–September		7–10 tropical cyclones
June 27, 2023	PAGASA	October–December		4–7 tropical cyclones
2023 season	Forecast Center	Tropical cyclones	Tropical storms	Typhoons	Ref.
Actual activity:	JMA	24	13	8
Actual activity:	JTWC	13	13	10
Actual activity:	PAGASA	9	7	6

During the year, several national meteorological services and scientific agencies forecast how many tropical cyclones, tropical storms, and typhoons will form during a season and/or how many tropical cyclones will affect a particular country. These agencies included the Tropical Storm Risk (TSR) Consortium of University College London, PAGASA and Taiwan's Central Weather Bureau.

The first forecast was released by PAGASA on January 13, 2023, in their monthly seasonal climate outlook predicting the first half of 2023. They predicted that only 0–2 tropical cyclones were expected to form or enter the Philippine Area of Responsibility between January and March, while 2–4 tropical cyclones are expected to form between April and June. PAGASA also stated that weakening La Niña conditions could last until it transitions back into ENSO-neutral conditions afterwards.

On May 5, Tropical Storm Risk (TSR) issued its first forecast for the 2023 season with moderate to strong El Niño expected to develop and persist through October, TSR predicted that tropical activity for 2023 will be above average predicting 29 named storms, 19 typhoons and 13 intense typhoons. The TSR remained constant with their prediction except slightly decreasing the intense typhoon numbers to 12 in the July forecast. In the last August forecast, the TSR increased the number of typhoons and intense typhoons to 20 and 14.

Seasonal summary

Early season activity

The first two months were inactive, with no tropical cyclones formed. It started with a tropical depression on March 4, being the first system of the season, formed to the east of Singapore designated as 98S by the JTWC due to the agency analyzing the system as being located within the Southern Hemisphere. It killed at least four people. In early April, a depression formed and was named Amang, which became the first named storm by PAGASA. It made its first landfall in Panganiban, Catanduanes around 23:00. It made its second landfall over Presentacion, Camarines Sur and in the vicinity of Lagonoy, Camarines Sur later that day.

It was downgraded to a low on April 13 because of unfavorable conditions including dry air and high wind shear. Amang caused over ₱50.84 million (US$923 thousand) of agricultural damages throughout its path. Another tropical depression formed on April 19, with JTWC giving it a high chance of developing into a tropical cyclone. The agency upgraded the system to a tropical storm on April 20 and three hours later, the JMA assigned the name Sanvu, making it the first named storm of the season. Sanvu began to weaken on April 22 due to clusters of convection on its northeast quadrant absorbing its energy. The JTWC subsequently ceased issuing bulletins on the storm.

In early May, a tropical disturbance developed around 745 km (460 mi) east of Davao City, naming it as Invest 93W by the JTWC. The convection continued to broaden as it wrapped around the disorganized low pressure area. However, land interaction and the system's weak structure hindered further development, despite being in favorable environmental conditions. Later on May 5, the JMA classified the disturbance as a tropical depression. Its chances of being a tropical cyclone were downgraded to low due to of presence of dry air and weak outflow, before it dissipated on May 7.

A low-pressure area formed south-southwest of Chuuk Islands and then developed into a tropical depression on May 19. It was later designated as 02W by the JTWC and named the storm "Mawar" a few hours later by the JMA before it intensified into a severe tropical storm on the next day. As it entered more favorable conditions and low wind shear, it was upgraded into category 1-equivalent typhoon by the JTWC. JMA followed suit and upgraded Mawar to Typhoon status at 03:45 UTC on May 21. Mawar rapidly intensified into the season's first super typhoon, before undergoing an eyewall replacement cycle and slightly weakening as it passed through the Mariana Islands.

After a close pass from Guam, Mawar regained super typhoon intensity and climaxed as a powerful Category 5 storm. It then entered the Philippine Area of Responsibility and was named Betty. Betty (Mawar) weakened later on due to dry air intrusions and unfavorable conditions, passing a hundred kilometers due east of the Batanes Islands and then weakening into a severe tropical storm as it made its way out of PAR. Mawar then began its extratropical transition as it shot off to the northeast.

In the first weeks of June, a low-pressure area was formed north of Palau, naming the system as Invest 98W. At the following day, it intensified and entered the Philippine area of responsibility, prompting to name the PAGASA as Chedeng at 08:00 UTC. The JTWC later followed suit and designated it as 03W. At 20:00 UTC, Chedeng was upgraded into a tropical storm, attaining the name Guchol. Guchol later became a strong Category 2 typhoon in the Philippine Sea, but the cold wake from Super Typhoon Mawar kept it from intensifying any further. As Guchol (Chedeng) exited the PAR, it weakened into a severe tropical storm, and continued northeastwards, avoiding the Japanese archipelago.

After weeks of inactivity, on July 12, the JTWC began monitoring a weak monsoon depression that is moving slowly towards northern Luzon. JMA followed suit and classified the disturbance as a tropical depression on the next day and took note that the system is just off the coast of Aurora, Philippines. PAGASA also started to issue advisories, which later named its local name Dodong. On July 14, PAGASA noted that it made landfall in Dinapigue, Isabela. As it became better organized in the West Philippine Sea and began moving over favorable environment, JTWC started to issue advisories on Dodong, with its designation as 04W.

Prior to exiting the PAR, JMA later upgraded into Tropical Storm Talim as it moved away from the Philippines. Talim then steadily intensified in the South China Sea, later reaching severe tropical storm intensity as it approached Southern China. The Joint Typhoon Warning Center then upgraded Talim to a Category 2 typhoon as it made landfall on Guangdong in China. Typhoon Talim then weakened inland, dissipating on July 19.

Mid/peak season activity

File:Doksuri and 06W on 2023-07-27.jpg

Typhoon Doksuri (Egay) after it recently passed by the Babuyan Islands and approached Taiwan and China, and the disturbance that eventually became the long-lived Typhoon Khanun (Falcon) as it developed over the Philippine Sea near the island of Palau on July 27

On July 16, as Tropical Storm Talim was headed for landfall in mainland China, a low pressure area which was originally a cloud cluster formed east of Mindanao. On July 19, a tropical depression formed and the JTWC designated it as Invest 98W. It was immediately named as Doksuri by the JMA and Egay by the PAGASA on the next day. On July 21, the system intensified into a tropical storm, and the very next day on July 22, the PAGASA upgraded it into a tropical storm.

Egay moved steadily westwards, approaching the Bicol Region and prompting Signal #2 warnings on some parts of the peninsula. Initially expected to strike Taiwan, Doksuri's track shifted more south over time. Doksuri then intensified into a typhoon on July 23, and during which, it began a period of rapid intensification, reaching Category 4 status later on. The PAGASA then upgraded 'Egay' (Doksuri) into a super typhoon, becoming the second to do so this year after Typhoon Mawar (Betty) and prompting the raising of Signal #5 over the Babuyan Islands later in the day, the first time since Typhoon Noru (Karding) struck Central Luzon the previous year. Doksuri then weakened back into a typhoon prior to making landfall in the early morning hours of July 26 on Fuga Island, Aparri as a powerful Category 4.

Doksuri then moved at snail's pace, bashing parts of Northern Luzon with typhoon-force winds for the rest of the day, whilst due to the slow movement, dropped torrential amounts of rainfall over the provinces of Ilocos Norte, Ilocos Sur, Abra and Cagayan, sinking many towns, villages and houses under floodwaters. By morning of July 26, Doksuri made a second landfall over Dalupiri Island, Aparri, Cagayan. The storm further weakened and was back to Category 1 intensity by the evening. Doksuri enhanced the Southwest Monsoon which brought rains and gusty conditions to most of western Luzon, including Mimaropa and Western Visayas, as well as Bataan and Zambales.

By the following day, Doksuri exited the Philippine Area of Responsibility, but with Tropical Cyclone Wind Signals still raised for the Ilocos Region, which was later slowly removed as the storm moved further away from the country, causing billions of pesos in damages. Doksuri, now in the South China Sea, exhibited another round of rapid intensification, forming a pinhole eye whilst southwest of Taiwan. It reintensified and managed to regain Category 3 status before an eyewall replacement cycle made it weaken, as it made landfall in Fujian in China. Doksuri also dropped torrential amounts of rainfall over China, dissipating inland by July 29, with its remnants causing continuous torrential rain, causing more flooding and destruction.

Whilst Doksuri was pounding Luzon with strong winds, a new area of low pressure formed near Palau on July 26. It was later upgraded to a tropical depression by the Japan Meteorological Agency, and the JTWC followed suit soon after, giving it the designation of 06W. 06W then later intensified into a tropical storm, and was named Khanun by the JMA. Khanun moved slowly towards the west-northwest in the Philippine Sea, entering the PAGASA's area of responsibility by July 29 and was given the domestic name of Falcon.

Khanun then later intensified into a severe tropical storm by Sunday, and underwent a period of rapid intensification east of the Philippines, becoming a typhoon not so long after. Khanun then continued its intensification whilst moving north-northwestward, reaching Category 4 status by Monday. By Tuesday, Khanun had maintained its intensity south of the Okinawa Islands. At 3:30 pm PHT (19:00 UTC), PAGASA declared that Falcon (Khanun) had exited its area of responsibility. Khanun then moved towards the Ryukyu Islands, weakening slightly back into a high-end Category 3, battering the islands with strong winds and heavy rains. Khanun then developed a very large eye, and moved slowly nearby the Ryukyu Islands, causing tremendous upwelling and its eventual weakening into a tropical storm. After stalling by that area for a few days and moving at snail's pace, Khanun then headed northwest, striking Korea and by the next day, its long life cycle had ended inland the Korean Peninsula.

At the meantime, Lan formed on August 8. It would later rapidly intensify into a very strong typhoon, on August 11. On August 12, Hurricane Dora crossed over from Central Pacific and was immediately classified as a typhoon, while gradually deteriorating.

By August 20, an area of convection east of Taiwan began moving southwestwards with little organization over its center. The PAGASA marked the system as a low pressure area on August 22, and the Japan Meteorological Agency upgraded it to a tropical depression. The PAGASA initially expected the system to not develop into a tropical cyclone and expected its dissipation by Friday, but later upgraded it into a tropical depression the next day, and was given the local name of Goring, it was also given a Tropical Cyclone Formation Alert by the JTWC, designated as 09W. Goring then moved generally north-northwestwards across the Philippine Sea.

On August 24, Goring was upgraded to a tropical storm by the JTWC, with the JMA following suit a few hours later at 06:00 UTC, receiving the name Saola. PAGASA also followed suit in upgrading the system into a tropical storm in their 17:00 PHT (09:00 UTC) update. Saola continued to intensify and began to move southwestwards over the Philippine Sea east of the Batanes Islands. PAGASA then started to issue Tropical Cyclone Wind Signals across the eastern parts of Northern Luzon on Friday morning.

A few hours later, the JTWC upgraded Saola into a typhoon, with the JMA upgrading the system to a severe tropical storm shortly thereafter. Saola was then later upgraded into a typhoon moments later by the JMA, with JTWC upgrading it to a Category 2, beginning a process of rapid intensification. PAGASA followed suit by the evening and upgraded Saola into a typhoon as well. Saola was then upgraded to a Category 4 typhoon by the morning of August 27. In the early morning hours of Sunday, PAGASA then upgraded Goring (Saola) into a super typhoon after its winds passed 185 km/h (115 mph), becoming the third storm to enter in their 'super typhoon' category this year.

Saola then executed a south-southeastward turn over the Philippine Sea. Saola then weakened back into a typhoon per PAGASA, with Tropical Cyclone Wind Signal #2 and #3 being lifted as it moved away from Central Luzon. The Joint Typhoon Warning Center also downgraded Saola back into a Category 2 typhoon. Saola then weakened due to an eyewall replacement cycle, and PAGASA dropped some tropical cyclone wind signals in Eastern Luzon. It then turned northwest, and PAGASA reissued Signal 4 for parts of the Babuyan Islands and then explosively intensified into a Category 4 super typhoon, per the Joint Typhoon Warning Center.

PAGASA then followed suit and upgraded Saola (Goring) into a super typhoon once more as it was passing between the Bashi Channel, and issued Signal #5 in the northeastern portion of the Babuyan Islands, the second time this year since Typhoon Doksuri a month earlier. Later that day, Saola crossed the northwestern boundaries of the Philippine Area of Responsibility, and PAGASA issued their final tropical cyclone advisories on it, with storm signals being dropped moments later. Saola remained a powerful super typhoon as it crossed into the South China Sea southwest of Taiwan. On the afternoon of August 31 (UTC), the JTWC noted that Saola was struggling to complete an eyewall replacement cycle, resulting in some slight weakening, however Saola had held onto the status of a 'super typhoon' on the JTWC scale. Meanwhile, Saola had weakened below the threshold for Violent Typhoon on the JMA scale that same afternoon. Around the same time, the Hong Kong Observatory had announced that tropical cyclone warning signal number 8 (Gale or Storm) would be issued at 2:40 a.m local time on Friday, with the potential of this being raised to warning signal number 10 (Hurricane) as Super Typhoon Saola drew closer.

It was warned that at some locations storm surges due to Super Typhoon Saola could reach historic levels, rivaling those of Typhoon Wanda in 1962 and Typhoon Hato in 2017. This has since been upgraded at 6:20 pm to an increasing gale or storm signal number 9, and later to the Hurricane Signal number 10 at 8:15 pm, becoming the first time in 5 years that the highest warning signal was raised since Typhoon Mangkhut (Ompong) back in 2018. Saola continued approaching near Southern China including Hong Kong. Saola then passed south of Hong Kong and Macau as a strong Category 4, battering the area with strong winds and heavy rain. Saola then weakened into a Category 3 as it made landfall in Guangdong, China on early Saturday. After its landfall, Saola weakened into a strong Category 2 typhoon. The Japan Meteorological Agency then downgraded Saola into a severe tropical storm a few hours after landfall. The JTWC later followed suit & downgraded Saola into a tropical storm by their next update as it moved further inland Guangdong. As convection waned over its center, the agencies downgraded the once powerful Saola into a tropical depression by September 2. Saola had dissipated on September 3, with its remnants causing rainfall and stormy conditions across Southern China.

The Western Pacific basin was then getting heated by late August. Typhoon Saola was then exhibiting a counter-clockwise loop east of the Philippines, a new broad low pressure area developed into a tropical depression on August 27, near the Northern Mariana Islands, while slowly drifting westward. On August 28, the JMA subsequently upgraded the system into a tropical storm, naming it Haikui. The JTWC began initiating advisories thereafter and was designated as 10W. Haikui then rapidly strengthened into the severe tropical storm category a few minutes later. As it moved west-northwest, Haikui entered the Philippine area of responsibility at around 21:00 PHT (13:00 UTC) and was given the domestic name Hanna. Haikui then maintained its severe tropical storm status for about a day while moving generally westwards across the Philippine Sea, before finally reaching typhoon status on September 1. Haikui then continued westwards over the Philippine Sea with little change in intensity but later intensified into a Category 2-equivalent typhoon a day later. Typhoon Haikui then began an episode of rapid intensification by September 3 at least 18 hours before landfall, becoming a strong Category 3 typhoon. Haikui struck Taitung County, Taiwan as a Category 3, becoming the first storm to hit mainland Taiwan for the first time in 4 years after Severe Tropical Storm Bailu (Ineng) and the first Category 3+ typhoon to hit the island since Typhoon Megi (Helen) in 2016.

A new tropical depression then formed near the far-eastern Pacific near the Micronesian Islands. It then intensified into Tropical Storm Kirogi as it moved north northwestward into the Pacific. It almost reached typhoon strength but wind shear stopped Kirogi from intensifying any further. Kirogi then weakened into a tropical storm as it neared Japan.

Systems

Tropical Depression Amang

Tropical depression (JMA)
150px 150px
Duration	April 10 – April 13
Peak intensity	55 km/h (35 mph) (10-min)  1004 hPa (mbar)

The JMA first noted a low-pressure area in the Philippine Sea on April 7. A strong convection to the north of the system's low-level circulation center (LLCC) prompted the JTWC to first issue a Tropical Cyclone Formation Alert (TCFA) on the disturbance as it tracked west-northwestwards into a favorable environment for further development. Later that day, the JMA and the PAGASA classified the storm as a tropical depression. As the storm formed within the Philippine Area of Responsibility (PAR), the depression received the name Amang.

Amang made its first landfall over Panganiban, Catanduanes around 23:00 PHT (15:00 UTC) on April 11. Later the next day, the PAGASA reported that Amang had made a second landfall in Presentacion, Camarines Sur and later made its third landfall in Lagonoy, Camarines Sur. Upon land interaction, the JTWC canceled its TCFA, stating that Amang had reached more unfavorable conditions including dry air and wind shear. PAGASA downgraded the storm to a low on April 13.

Agricultural damages caused by the storm were estimated at ₱50.84 million (US$923 thousand), affecting 1,569 farmers and 1,330 ha (3,300 acres) of land. 1,918 passengers were stranded in the Bicol Region following sea travel suspensions. On April 13, classes up to senior high school in 19 areas were suspended due to bad weather, along with pre-elementary classes in areas under Signal No. 1.

Tropical Storm Sanvu

Tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration	April 19 – April 22
Peak intensity	85 km/h (50 mph) (10-min)  996 hPa (mbar)

An area of convection monitored by the JTWC spawned south-southeast of Pohnpei on April 18. The JMA later classified the disturbance as a tropical depression the following day, before the JTWC followed suit and designated the system 01W. On April 20, the depression further intensified to a tropical storm, according to the JTWC, after convection and rainbands strengthened over the LLCC. The JMA subsequently upgraded its status by 6:00 UTC, and gave the name Sanvu to the storm.

After reaching its peak intensity early on April 21, Sanvu began to weaken afterward due to clusters of convection on its northeast quadrant absorbing its energy. By April 22, Sanvu's poor, ragged structure of its circulation center prompted the JTWC to cease issuing bulletins on the storm as it was downgraded to a tropical depression. The JMA cancelled advisories on the storm the same day as well. The JMA tracked the system until 00:00 UTC of April 25. The JTWC reported that Sanvu's remnants had dissipated on April 26.

Typhoon Mawar (Betty)

Typhoon (JMA)
Category 5 super typhoon (SSHWS)
150px 150px
Duration	May 19 – June 2
Peak intensity	215 km/h (130 mph) (10-min)  900 hPa (mbar)

Main article: Typhoon Mawar

On May 17, a weak low-level circulation (LLC) located 865 km (535 mi) south of Guam was marked by the JTWC. Global forecast models such as the Global Forecast System and Navy Global Environmental Model indicated that the disturbance would gradually intensify into a tropical cyclone in the upcoming days. Later the JTWC issued a TCFA on the disturbance after thunderstorms became very wide and organization had improved. The JMA also began tracking the system, marking it as LPA. shortly before upgrading it to a tropical depression on May 19. The JTWC followed suit on May 20 after the depression had strengthened from warm sea surface temperatures and poleward and westward outflow, designating it 02W. The same day, the depression upgraded to a tropical storm. The JMA assigned the name Mawar to the storm. The JMA further upgraded the storm to severe tropical storm status at 00:00 UTC of May 21, as the deep convection in the CDO completely obscured the LLCC. Both the JMA and JTWC upgraded Mawar to a typhoon on May 21. Mawar further became a super typhoon and underwent an eyewall replacement cycle after reaching winds of 250 km/h (155 mph). During May 24, the center of Mawar passed about north of the northern tip of Guam, around 9 p.m. local time and slightly weakened.

Soon afterwards, Mawar reached its peak intensity, attaining 1-minute sustained winds of 295 km/h (185 mph), equivalent to Category 5 strength on the SSHWS, and 10-minute sustained winds of 215 km/h (130 mph) along with the barometric pressure of . Mawar entered the PAR, which PAGASA assigned it the name Betty. Mawar slightly weakened moving around the southwestern edge of the subtropical high. As a result, Mawar weakened into a severe tropical storm as the JMA reported on May 31, before exiting the PAR on June 1. Mawar become a tropical storm on June 2, as it approached Okinawa. On June 3, Mawar became an extratropical cyclone south of Honshu, as it moved towards the open Pacific.

Power outages began affecting parts of Guam on May 22 as winds from Mawar intensified. Guam International Airport also recorded winds up to 104.7 miles per hour (168.5 km/h) as Mawar impacted the island. The Weather Prediction Center recorded that multiple locations in Guam received at least 20 inches (51 cm) of rain during Typhoon Mawar, with most of it falling in just three hours.

Typhoon Guchol (Chedeng)

Typhoon (JMA)
Category 2 typhoon (SSHWS)
150px 150px
Duration	June 6 – June 12
Peak intensity	150 km/h (90 mph) (10-min)  960 hPa (mbar)

In the first weeks of June, a low-pressure area was formed north of Palau, naming the system as Invest 98W. The low-pressure area north of Palau then developed into a tropical depression late on June 5. At the following day, it intensified and entered the Philippine area of responsibility, prompting to name the PAGASA as Chedeng at 08:00 UTC. The JTWC later followed suit and designated it as 03W.

At 20:00 UTC, Chedeng was upgraded into a tropical storm, attaining the name Guchol. Guchol later became a strong Category 2 typhoon in the Philippine Sea, but the cold wake from Super Typhoon Mawar kept it from intensifying any further. As Guchol (Chedeng) exited the PAR, it weakened into a severe tropical storm, and continued northeastwards, avoiding the Japanese archipelago. It then became extratropical on June 12.

Guchol had minimal impact. However, the Southwest monsoon was enhanced during the presence of Guchol inside Philippine area of responsibility, resulting in widespread heavy rains over the western portions of Luzon.

Severe Tropical Storm Talim (Dodong)

Severe tropical storm (JMA)
Category 2 typhoon (SSHWS)
150px 150px
Duration	July 13 – July 18
Peak intensity	110 km/h (70 mph) (10-min)  970 hPa (mbar)

Main article: Tropical Storm Talim (2023)

On July 12, the JTWC began tracking a weak monsoon depression 298 nautical miles (552 km; 343 mi) east of Manila, slowly moving towards northern Luzon. On July 13, the JMA took note of a low-pressure area just off the coast of Aurora, Philippines. A few hours later at 12:00 UTC, the JMA recognized the formation of a tropical depression. The PAGASA issued a similar announcement, and subsequently named the system Dodong. It made first landfall in Dinapigue, Isabela a few hours later. The system continued to track westward close to the northern edge of mainland Luzon, crossing through Cagayan and Ilocos Norte. It emerged off the coast of Ilocos Norte on July 14 at 09:00 UTC (17:00 PHT). Around 15:00 UTC, the JTWC began issuing advisories for the now-tropical depression, and designated the system as 04W. The system intensified into a tropical storm just prior to exiting the PAR and was subsequently named Talim by the JMA. On July 15, Talim left the PAR while it maintained its strength which was announced by the PAGASA in its final bulletin. The system had a broad LLCC with deep convection persisting along the western and southern periphery. Talim continued to intensify in the South China Sea, later being upgraded into a severe tropical storm.

Talim moved west-northwestward within a favorable environment was being offset by equatorward outflow. The JTWC's assessed the storm to have strengthened into of winds. Talim made its second landfall in Zhanjiang, Guangdong, with winds of 136 km/h (85 mph) on July 17. As it moved further inland, Talim rapidly weakened. Shortly after the landfall, the JTWC discontinued warnings on the system. Talim dissipated early on the next day.

Winds from Talim enhanced the East Asian monsoon over the Philippines and brought heavy rainfall and gusty conditions over the country as it neared Luzon. Classes in three cities and in Cagayan were suspended as the storm crossed Luzon. Three domestic flights were cancelled. Three people were killed by the storm.

Typhoon Doksuri (Egay)

Main article: Typhoon Doksuri

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px 150px
Duration	July 19 – July 29
Peak intensity	185 km/h (115 mph) (10-min)  925 hPa (mbar)

On July 19, JMA began tracking a low pressure area in the Philippine Sea, east of Mindanao. The agency noted its formation into a tropical depression by July 20. JTWC then released a TCFA on the storm later that day. On July 21, the system intensified into a tropical storm and was named Doksuri. The PAGASA also noted the storm's formation and locally named it Egay. The JTWC subsequently initiated advisories on the system and classified it as 05W. Doksuri slightly intensified as it tracked northwestward across the following day. At 12:00 UTC on July 23, Doksuri began to rapidly intensify as it reached super typhoon status over the Philippine Sea. Doksuri traversed through the extreme northern Philippines across the night, weakening into a typhoon and later making landfall at Camiguin Island and later in Fuga Island in Aparri, Cagayan. Doksuri made a third landfall over Dalupiri Island on July 26, moving very slowly as it did so, dropping massive amounts of rainfall over the Ilocos Region and other parts of Northern Luzon. Doksuri left the PAR at around 10:00 PHT (02:00 UTC) on July 27. Doksuri then began to ensue another round of rapid intensification, forming a pinhole eye Doksuri moved northwestward and subsequently made its fourth and final landfall in Jinjiang, Fujian, with two-minute sustained winds of 180 km/h (50 m/s) on July 28. Doksuri rapidly weakened once inland and dissipated shortly thereafter.

Overall, the typhoon was responsible for 137 deaths, 46 missing and 285 injured, including 27 people on board the MB Aya Express who were killed when the pump boat capsized and caused $15.5 billion in damage across several countries.

Typhoon Khanun (Falcon)

Main article: Typhoon Khanun (2023)

Typhoon (JMA)
Category 4 typhoon (SSHWS)
150px 150px
Duration	July 26 – August 11
Peak intensity	175 km/h (110 mph) (10-min)  930 hPa (mbar)

On July 26, the JMA announced the formation of a low-pressure area in the Pacific Ocean. The JMA started warning the system, declaring it a tropical depression. Analysis from the JMA indicated that the system was in a favorable environment for development, with warm sea surface temperatures and low vertical wind shear. The JMA and the JTWC upgraded the system to a tropical storm, with the JMA assigning the name Khanun for the system. Khanun consolidating LLCC with formative convective banding and deep convection over the eastern semicircle. Khanun entered the PAR around 03:00 UTC (11:00 PHT) on July 29, and was named Falcon by the PAGASA. Over 24 hours, its maximum sustained wind speeds grew by and eventually reached a peak of , equivalent to Category 4 status on the Saffir–Simpson scale. Khanun left the PAR at around 03:00 PHT (19:00 UTC) on August 1. Satellite imagery showed a consolidating LLCC with formative convective banding and deep convection over the northern semicircle. Around 00:00 UTC on August 10, Khanun made landfall on Geojedo Islands in South Korea with winds of . The JMA continued to monitor Khanun as a tropical cyclone until early on August 11.

As of August 18, 13 deaths were reported and 16 are reported to have gone missing following the typhoon, another 115 remain injured, and damage totaled at US$98.1 million. At least 160,000 homes lost power across the island chain. Khanun became the first to pass through the Korean Peninsula from south to north since recordkeeping began in 1951. Although Khanun did not directly affect the Philippines, both Khanun and Typhoon Doksuri enhanced the monsoon for several days, which caused severe flooding throughout the country.

Typhoon Lan

Typhoon (JMA)
Category 4 typhoon (SSHWS)
150px 150px
Duration	August 5 – August 17
Peak intensity	165 km/h (105 mph) (10-min)  940 hPa (mbar)

Main article: Typhoon Lan (2023)

On August 5, the JMA reported that a low-pressure area had formed east-northeast of Iwo Jima. Deep convection shifted towards the southeastern semicircle of the circulation, while the still-poorly defined center. Environmental conditions were assessed as being marginally conducive for tropical cyclogenesis, with warm sea surface temperatures (SST) near 29–30 °C (84–86 °F) and low vertical wind shear, and good equatorward outflow. At the same time, the JMA upgraded it to a tropical depression, before the JTWC issued a TCFA on the system. Later that day, the agency upgraded to a tropical storm, with the JMA assigning the name Lan for the system. Lan continued to strengthen as it turned more westward under the influence of the SST and weak vertical wind shear, the JMA upgraded Lan to a severe tropical storm at 06:00 UTC on August 9 as its maximum sustained winds increased to . Lan began to intensify more quickly, reaching typhoon status. The JTWC upgraded it to Category 4-equivalent typhoon on August 11 after Dvorak estimates indicated winds of . Lan was rapidly decaying as the storm struggled to −60 °C (−76 °F) the cold ring that surrounded the eye. The storm maintained its overall convective structure, but the waters beneath the cyclone cooled, prompting a quick weakening trend. Around 19:00 UTC on August 14, Lan made landfall near Cape Shionomisaki in Japan. Lan emerged back over the southern Sea of Japan. The JMA issued its last advisory on Lan, and declared it an extratropical low on August 17.

The JMA issued purple heavy rain—the second highest level on a four-tier scale—and landslide warnings for parts of Kyoto Prefecture in Kansai region and Iwate Prefecture in Tōhoku region as of late August 14. Typhoon Lan caused widespread damage. In addition to causing landslides and flooding, the storm also uprooted trees and damaged electrical lines. At least 100,000 homes are without power, and more than 237,000 individuals have been forced from their homes. One person has been reported dead and 64 are reported to have remained injured following the typhoon.

Typhoon Dora

Typhoon (JMA)
Category 2 typhoon (SSHWS)
150px 150px
Duration	August 12 (entered basin) – August 21
Peak intensity	150 km/h (90 mph) (10-min)  975 hPa (mbar)

On August 11, a weakening Hurricane Dora moved into the basin from the Central Pacific basin. At 00:00 UTC, August 12, the JMA and the JTWC initiated advisories on Dora, declaring that it had just crossed the International Date Line and classifying it as a typhoon. The cloud tops further warmed and its eye vanished from satellite imagery. Dora showed significant deterioration along the system's northern flank. Dora became increasingly sheared by early August 13, interacting with an upper-level trough. Vertical wind shear exceeded . Further decay in the organization of the storm's deep convection caused Dora to be downgraded to a tropical storm. With Dora's ragged center, the system remained disorganized, as wind shear was becoming displaced to the east. By the early hours of August 15, both agencies issued their final warnings on Dora; its LLCC further became broad and exposed. The JMA, however, continued to monitor the system until it was last noted on 18:00 UTC of August 21.

Severe Tropical Storm Damrey

Severe tropical storm (JMA)
Category 1 typhoon (SSHWS)
150px 150px
Duration	August 21 – August 29
Peak intensity	95 km/h (60 mph) (10-min)  985 hPa (mbar)

On August 21, the JMA started tracking a tropical depression in the open Western Pacific. The JTWC then followed suit on August 23 by upgrading the system into a tropical depression, and designating it as 08W. The JMA later upgraded the system into a tropical storm on August 24, receiving the name Damrey, with the JTWC following suit later on August 25. It gradually intensified as it moves northward, becoming a severe tropical storm and Category 1-equivalent typhoon, by the JMA and the JTWC, respectively, well east of Japan, on August 27. It turned post-tropical on August 29.

The remnants of the storm delivered high winds in Alaska, with a 69 mph (111 km/h) wind gust in Potter Marsh and 43 mph (69 km/h) gust at Ted Stevens Anchorage International Airport. High winds hit the Anchorage Bowl on Thursday, knocking out power to thousands as the remnants blow in the Southeastern Alaska. Strong winds downed trees throughout town that hit power lines and caused outages.

Typhoon Saola (Goring)

Main article: Typhoon Saola (2023)

Typhoon (JMA)
Category 4 super typhoon (SSHWS)
150px 150px
Duration	August 22 – September 3
Peak intensity	195 km/h (120 mph) (10-min)  920 hPa (mbar)

By August 20, an area of convection east of Taiwan began moving southwestwards with little organization over its center. The PAGASA initially expected the system to not develop into a tropical cyclone, but later upgraded it into a tropical depression the next day, and was given the local name of Goring, it was also given a Tropical Cyclone Formation Alert by the JTWC, designated as 09W. Goring then moved generally north-northwestwards across the Philippine Sea. On August 24, Goring was upgraded to a tropical storm by the JTWC, with the JMA following suit a few hours later at 06:00 UTC, receiving the name Saola. Saola continued to intensify and began to move southwestwards over the Philippine Sea east of the Batanes Islands. A few hours later, the JTWC upgraded Saola into a typhoon, with the JMA upgrading the system to a severe tropical storm shortly thereafter. Saola was then later upgraded into a typhoon moments later by the JMA, with JTWC upgrading it to a Category 2, beginning a process of rapid intensification. PAGASA followed suit by the evening and upgraded Saola into a typhoon as well. Saola was then upgraded to a Category 4 typhoon by the morning of August 27.

After it executed a south-southeastward turn over the Philippine Sea. Saola weaken back into a category-2 typhoon. However, on August 29, it then explosive intensified again into a Category 4 super typhoon while crossing the northwestern boundaries of the Philippine Area of Responsibility. Saola remained as a powerful super typhoon while approaching Hong Kong and China. Prior to the arrival of the typhoon, Hong Kong Observatory issued Hurricane Signal No. 10 at 20:15 HKT, September 1, the first time in 5 years since Typhoon Mangkhut (Ompong) in 2018. It passed south of Macau and Hong Kong, battering gusty winds and heavy rains. Saola weakened into Category 3 before making landfall over Guangdong, China. As it moves inland, Saola weakened into severe tropical storm and later tropical depression by September 2 before it dissipated on September 3.

Typhoon Haikui (Hanna)

See also: 2023 Hong Kong rainstorm and floods

Typhoon (JMA)
Category 3 typhoon (SSHWS)
150px 150px
Duration	August 27 – September 6
Peak intensity	155 km/h (100 mph) (10-min)  955 hPa (mbar)

Whilst Typhoon Saola was exhibiting a counter-clockwise loop east of the Philippines, a new broad low pressure area developed into a tropical depression on August 27, near the Northern Mariana Islands, while slowly drifting westward. On August 28, the JMA subsequently upgraded the system into a tropical storm, naming it Haikui. The JTWC began initiating advisories thereafter and was designated as 10W. Haikui then rapidly strengthened into the severe tropical storm category a few minutes later. As it moved west-northwest, Haikui entered the Philippine area of responsibility at around 21:00 PHT (13:00 UTC) and was given the domestic name Hanna.

Haikui then maintained its severe tropical storm status for about a day while moving generally westwards across the Philippine Sea, before finally reaching typhoon status on September 1. Haikui then continued westwards over the Philippine Sea with little change in intensity but later intensified into a Category 2-equivalent typhoon a day later. Typhoon Haikui then began an episode of rapid intensification by September 3 at least 18 hours before landfall, becoming a strong Category 3 typhoon. Haikui struck Taitung County, Taiwan as a Category 3, becoming the first storm to hit mainland Taiwan for the first time in 4 years after Severe Tropical Storm Bailu (Ineng) and the first Category 3+ typhoon to hit the island since Typhoon Megi (Helen) in 2016. The collision between Typhoon Haikui & the mountain ranges of Taiwan considerably wrecked the structure of the storm and made it weaken back into a minimal Category 1 typhoon by the time it exited the landmass of the island in the evening. Haikui then moved erratically over the next few hours, heading eastwards and making a second landfall in Kaohsiung, Taiwan. Haikui then continued back on its westward course a few hours later. The typhoon left the Philippine Area of Responsibility on September 4, as it left the Taiwanese landmass. The JMA then downgraded Haikui back into a severe tropical storm as its circulation became degraded after the landfall.

Though not making any direct landfall in the Philippines, Typhoon Haikui (locally known as Hanna) enhanced the southwest monsoon along with Typhoon Saola, causing heavy rainfall and strong winds in many areas especially in Luzon, and causing one death. The PAGASA raised Signal #1 for the Batanes and Babuyan Islands as Haikui approached and its track, initially expected to make landfall in Eastern China, shifted southwards over time.

On September 5, Typhoon Haikui made landfall along the coast of Dongshan County, Fujian. Rainstorm to heavy rainstorm occurred in coastal areas of Fujian, causing the death of two firefighters.

On September 7, the remnants of Typhoon Haikui brought record breaking rainfall to Hong Kong. Hong Kong Observatory recorded 158 millimeters of rain between 11pm and midnight local time, the highest hourly rainfall rate since records began in 1884. Some parts of the city even accumulated over 900 mm of rainfall within just 24 hours. Four people were killed in Hong Kong as a result of the flash floods. Other parts of the Pearl River Delta, including Shenzhen and Macau, were also severely impacted.

Severe Tropical Storm Kirogi

Severe tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration	August 29 – September 6
Peak intensity	95 km/h (60 mph) (10-min)  992 hPa (mbar)

A low pressure area located far east of Guam developed on August 29, indicating that the system is in a favorable environment and low windshear. Over the next day, the JTWC started issuing advisories as it steadily upgrading into a tropical depression, which designated as 11W. Slowly intensifying while moving generally northwest, the system developed into a tropical storm, as announced by JTWC, on August 30. JMA followed suit shortly thereafter, giving it the name Kirogi. The storm slightly strengthened to a severe tropical storm. In the first month of September, JMA announced that it weakened back into a tropical storm before rapidly weakening on September 2. Its remnants meandered around Japan and interacted with Tropical Storm Yun-yeung for a few days before dissipating on September 6.

Kirogi didn't enter the PAR however, it enhanced the southwest monsoon along with Typhoons Saola (Goring) and Haikui (Hanna).

Tropical Storm Yun-yeung (Ineng)

Tropical storm (JMA)
Tropical storm (SSHWS)
150px 150px
Duration	September 4 – September 8
Peak intensity	85 km/h (50 mph) (10-min)  996 hPa (mbar)

From the bands of Typhoon Haikui, an area of low pressure formed in the Philippine Sea in early September. The low-pressure area intensified into a tropical depression on September 4 and was later named Ineng by the PAGASA. A day later, the Japan Meteorological Agency (JMA) upgraded Ineng into a tropical storm and was given the name Yun-yeung, which replaced Kai-tak. Shortly after being named, on September 6, Yun-yeung left the PAR at around 06:00 PHT (22:00 UTC). Yun-yeung continued to move northward slowly as it approaches central and eastern Japan. The JMA last noted Yun-yeung on 18:00 UTC of September 8.

Yun-yeung brought heavy rain across wide areas of Japan, prompting warnings over the risk of flooding and mudslides. Some train lines were impacted in the Kanto region on Friday. JR East suspended some lines and limited express trains on Friday, and multiple lines are experiencing delays.

Tropical Depression 13W

Tropical depression (JMA)
Tropical depression (SSHWS)
150px
Duration	September 24 – Present
Peak intensity	<55 km/h (35 mph) (10-min)  1004 hPa (mbar)

Other systems

See also: List of tropical cyclones near the Equator

Many of the tropical depressions of the season failed to intensify into tropical storms, or even be numbered.

File:JMA TD 04 2023-05-05 0545Z.jpg

219x219px

• According to the JMA, a tropical depression formed to the east of Singapore on March 4. It was designated 98S by the JTWC shortly afterwards, due to the agency analyzing the system as being located within the Southern Hemisphere. The system was last noted on March 7. 50,000 people were affected in Malaysia from the floods produced by the system, which also killed four people.
• On May 1, a tropical disturbance persisted around 740 km (460 mi) east of Davao City and had fragmented but organized rainbands to the north and west of its circulation center. The convection continued to broaden as it wrapped the disorganized LLCC. However, land interaction with the Philippines and the system's weak structure hindered further development, despite being in favorable environmental conditions. On May 5, the JMA classified the disturbance as a tropical depression. However, dry air and a weak outflow aloft showed that the depression had very little development, all while tracking west-northwestward. The depression later dissipated by May 7.
• On June 7, the JMA detected a broad area of circulation associated with a tropical disturbance north of Hainan. The agency dubbed it a tropical depression shortly after. However, by the next day, the system moved over China and the circulation center began deteriorating. The system was last noted on 18:00 UTC of June 11. Persistent rainfall in Guangxi caused the Baisha River to flood multiple villages in Hepu County. Firefighters used boats to rescue residents trapped in their homes. A total of 2,603 people required evacuation. On June 9, Vietnam's National Center for Hydrometeorological Forecasting (NCHMF) issued "Potential Tropical Depression Alert" in the Gulf of Tonkin, which warned the resurgence of this tropical depression but then discontinue monitoring on June 10.
• On August 3, a tropical depression formed to the west of Hainan. The system weakened on August 4.
• On August 19, a tropical depression formed to the southeast of Japan. The system dissipated on August 21.
• On September 3, a tropical depression formed but dissipated on the next day due to high wind shear despite being in a favorable condition.
• On September 4, the JMA started tracking a depression that originated from the tail-end of Tropical Storm Kirogi. The system was last noted on 06:00 UTC of September 6.
• On September 10, a tropical depression formed near the Ryukyu Islands. It meandered around the area for a few days before turning south and then northwest toward Taiwan. The system dissipated on September 14.
• The JMA briefly tracked a tropical depression that persisted to the northeast of the Mariana Islands on September 12.

Storm names

See also: Tropical cyclone naming and History of tropical cyclone naming

Within the Northwest Pacific Ocean, both the Japan Meteorological Agency (JMA) and the Philippine Atmospheric, Geophysical and Astronomical Services Administration (PAGASA) assign names to tropical cyclones that develop in the Western Pacific, which can result in a tropical cyclone having two names. The Japan Meteorological Agency's RSMC Tokyo — Typhoon Center assigns international names to tropical cyclones on behalf of the World Meteorological Organization's Typhoon Committee, should they be judged to have 10-minute sustained windspeeds of 65 km/h (40 mph).

PAGASA names to tropical cyclones which move into or form as a tropical depression in their area of responsibility located between 135°E and 115°E and between 5°N and 25°N even if the cyclone has had an international name assigned to it. The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee. Should the list of names for the Philippine region be exhausted then names will be taken from an auxiliary list of which the first ten are published each season. Unused names are marked in gray. The names of significant tropical cyclones will be retired by both PAGASA and the Typhoon Committee in the spring of 2024.

International names

Main article: List of retired Pacific typhoon names

A tropical cyclone is named when it is judged to have 10-minute sustained windspeeds of 65 km/h (40 mph). The JMA selected the names from a list of 140 names, that had been developed by the 14 members nations and territories of the ESCAP/WMO Typhoon Committee. During the season, the name Yun-yeung was used for the first time after it replaced the name Kai-tak, which was retired after the 2017 season. Retired names, if any, will be announced by the WMO in 2024; though replacement names will be announced in 2025. The next 28 names on the naming list are listed here along with their international numeric designation, if they are used.

Sanvu (2301) Mawar (2302) Guchol (2303) Talim (2304) Doksuri (2305) Khanun (2306) Lan (2307)

Saola (2309) Damrey (2310) Haikui (2311) Kirogi (2312) Yun-yeung (2313) Koinu (unused) Bolaven (unused)

Sanba (unused) Jelawat (unused) Ewiniar (unused) Maliksi (unused) Gaemi (unused) Prapiroon (unused) Maria (unused)

Son-Tinh (unused) Ampil (unused) Wukong (unused) Jongdari (unused) Shanshan (unused) Yagi (unused) Leepi (unused)

If a tropical cyclone enters the Western Pacific basin from the Eastern and Central Pacific basin (west of 180°E), it will retain the name assigned to it by the National Hurricane Center (NHC) and Central Pacific Hurricane Center (CPHC). The following storms were named in this manner.

• Dora (2308)

Philippines

Main article: List of retired Philippine typhoon names

This season, PAGASA will use its own naming scheme for storms that develop in or enter their self-defined area of responsibility. During this season, PAGASA is using the following list of names, that was last used during 2019 and will be used again in 2027, updated with replacements of retired names, if any. All of the names are the same as in 2019 except Tamaraw and Ugong, which replaced the names Tisoy and Ursula after they were retired.

Amang Betty (2302) Chedeng (2303) Dodong (2304) Egay (2305)

Falcon (2306) Goring (2309) Hanna (2311) Ineng (2313) Jenny (unused)

Kabayan (unused) Liwayway (unused) Marilyn (unused) Nimfa (unused) Onyok (unused)

Perla (unused) Quiel (unused) Ramon (unused) Sarah (unused) Tamaraw (unused)

Ugong (unused) Viring (unused) Weng (unused) Yoyoy (unused) Zigzag (unused)

Auxiliary list

Abe (unused) Berto (unused)

Charo (unused) Dado (unused)

Estoy (unused) Felion (unused)

Gening (unused) Herman (unused)

Irma (unused) Jaime (unused)

Season effects

This table summarizes all the systems that developed within or moved into the North Pacific Ocean, to the west of the International Date Line during 2023. The tables also provide an overview of a system's intensity, duration, land areas affected, and any deaths or damages associated with the system.

Name	Dates active	Peak classification	Sustained wind speeds	Pressure	Land areas affected	Damage (USD)	Deaths	Refs
TD	March 4–7	Tropical depression			Brunei, Indonesia, Malaysia, Singapore	5000000000000000000♠ Unknown	4
Amang	April 10–13	Tropical depression			Palau, Philippines	7005222975000000000♠$223 thousand	5000000000000000000♠ None
Sanvu	April 19–22	Tropical storm			Federated States of Micronesia	5000000000000000000♠ None	5000000000000000000♠ None
TD	May 5–7	Tropical depression	Not specified		Philippines	5000000000000000000♠ None	5000000000000000000♠ None
Mawar (Betty)	May 19 – June 2	Violent typhoon			Federated States of Micronesia, Guam, Northern Mariana Islands, Philippines, Ryukyu Islands	7008250000000000000♠$250 million	6
Guchol (Chedeng)	June 6–12	Typhoon			Philippines, Japan and Alaska	5000000000000000000♠ None	5000000000000000000♠ None
TD	June 7–11	Tropical depression	Not specified		South China, Vietnam	5000000000000000000♠ None	5000000000000000000♠ None
Talim (Dodong)	July 13–18	Severe tropical storm			Philippines, South China, Vietnam	7006578000000000000♠$5.78 million	3
Doksuri (Egay)	July 19–29	Very strong typhoon			Philippines, Taiwan, China	7010156466372614100♠$15.6 billion	137
Khanun (Falcon)	July 26 – August 11	Very strong typhoon			Philippines, Taiwan, Japan, South Korea, North Korea, Russia	7007981000000000000♠$98.1 million	13
TD	August 3–4	Tropical depression	Not specified		South China, Vietnam	5000000000000000000♠ None	5000000000000000000♠ None
Lan	August 5–17	Very strong typhoon			Bonin Islands, Japan	5000000000000000000♠ Unknown	1
Dora	August 12–21	Typhoon			Wake Island (after crossover)	5000000000000000000♠ None	5000000000000000000♠ None
TD	August 19–21	Tropical depression	Not specified		None	5000000000000000000♠ None	5000000000000000000♠ None
Damrey	August 21–29	Severe tropical storm			None	5000000000000000000♠ None	5000000000000000000♠ None
Saola (Goring)	August 22 – September 3	Violent typhoon			Philippines, South China, Macau, Taiwan, Hong Kong, Northern Vietnam	7007438666144700000♠$43.9 million	3
Haikui (Hanna)	August 27 – September 6	Very strong typhoon			Northern Mariana Islands, Taiwan, Philippines, China	5000000000000000000♠ Unknown	7000500000000000000♠ ≥5
Kirogi	August 29 – September 6	Severe tropical storm			Japan	5000000000000000000♠ None	5000000000000000000♠ None
TD	September 2–3	Tropical depression	Not specified		None	5000000000000000000♠ None	5000000000000000000♠ None
Yun-yeung (Ineng)	September 4–8	Tropical storm			Japan	5000000000000000000♠ None	5000000000000000000♠ None
TD	September 4–6	Tropical depression	Not specified		None	5000000000000000000♠ None	5000000000000000000♠ None
TD	September 10 – 14	Tropical depression	Not specified		None	5000000000000000000♠ None	5000000000000000000♠ None
TD	September 12	Tropical depression	Not specified		None	5000000000000000000♠ None	5000000000000000000♠ None
13W	September 24 - Present	Tropical depression	Not specified		None	5000000000000000000♠ None	5000000000000000000♠ None
Season Aggregates
24 systems	March 4 – Season ongoing					7010160446402364100♠$16 billion	167

See also

• Weather of 2023
• Tropical cyclones in 2023
• Pacific typhoon season
• 2023 Atlantic hurricane season
• 2023 Pacific hurricane season
• 2023 North Indian Ocean cyclone season
• South-West Indian Ocean cyclone seasons: 2022–23, 2023–24
• Australian region cyclone seasons: 2022–23, 2023–24
• South Pacific cyclone seasons: 2022–23, 2023–24

External links

• Japan Meteorological Agency
• China Meteorological Agency
• Digital Typhoon
• Hong Kong Observatory
• Joint Typhoon Warning Center
• Korea Meteorological Administration
• National Weather Service Guam
• Malaysian Meteorological Department
• Philippine Atmospheric, Geophysical and Astronomical Services Administration
• Taiwan Central Weather Bureau
• TCWC Jakarta (Indonesian)
• Thai Meteorological Department (Thai)
• Typhoon2000
• Vietnam's National Hydro-Meteorological Service