This page is currently being merged. Consensus to merge this pagewith Tropical Storm Lingling (2025) has been found. You can help implement the merge by following the resolution on the discussion and the merging instructions. Process started on September 2025.
The 2025 Pacific typhoon season is an ongoing event in the annual cycle of tropical cyclone formation in the western Pacific Ocean. The season will run throughout 2025, though most tropical cyclones typically develop between June and October. The season's first named storm, Wutip, developed on June 11, the fifth-latest date for a typhoon season to produce a named storm.[1]
The scope of this article is limited to the Pacific Ocean to the north of the equator between 100°E and the 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)[nb 2] will name a tropical cyclone if it has 10-minute sustained wind speeds of at least 65km/h (40mph) 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 United States' Joint Typhoon Warning Center(JTWC)[nb 1][nb 3] are given a number with a "W" suffix; W meaning west, a reference to the western Pacific region.
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, the PAGASA, Vietnam's National Center for Hydro-Meteorological Forecasting (NCHMF) and Taiwan's Central Weather Administration (CWA).
On May 7, 2025, the Tropical Storm Risk (TSR) issued its first extended-range forecast, predicting slightly below-average activity with 25 named storms, 15 typhoons, and 8 intense typhoons. The outlook was influenced by expected neutral ENSO conditions, strong easterly wind anomalies in April, the absence of early-season storm activity, and a continued negative phase of the Pacific decadal oscillation (PDO), all of which are factors typically associated with reduced typhoon activity.
TSR released its updated extended-range forecast on August 7, maintaining the number of named storms and typhoons but reducing the number of intense typhoons to 7. They also significantly decrease the predicted ACE index due to the lower-than-expected storm activity through June and July and the ongoing negative PDO phase.
Seasonal summary
Background
The 2025 Pacific typhoon season has no official season limit, although most tropical cyclones typically develop between June and October. So far, 30 tropical cyclones have formed, with 19 named storms. Eight of them have become typhoons, and one has become a super typhoon. The season's accumulated cyclone energy index, as calculated by the Colorado State University (CSU) using data from the JTWC, as of September 24, is 103.3 units.[7]
Early season activity
Three systems active on July24: Typhoon Co-may (far left); Tropical Storm Francisco (upper right); and Tropical Storm Krosa (lower right).
The Pacific typhoon season officially began with the formation of a tropical depression on February 11 near the Philippines. Nearly three months later, Tropical Storm Wutip formed on June 11, becoming the third-latest named storm in the western Pacific basin. It also ended a 169-day period during which no named storms were active in the basin. Wutip caused extensive damage in parts of the Philippines, Vietnam, and China, resulting in the deaths of 17 people and US$253 million in damage. On June 11, another low-pressure area formed east of the Philippines, becoming Tropical Depression Auring the next day. Auring moved northward and crossed Taiwan before weakening into a remnant low. On June 21, Tropical Depression 03W formed, and three days later, Tropical Storm Sepat formed off the coast of Japan.
July was very active, with eight named storms, including one that was not designated by the Japan Meteorological Agency (JMA). The month began with the formation of Tropical Storm Mun, which spared some areas. The first typhoon of the season, Danas, formed on July 3 and made landfall in Taiwan as a Category 1 typhoon, becoming the first typhoon to hit the island's west-central coast since Typhoon Wayne in 1986. On July 11, two tropical cyclones formed: Tropical Storm Nari and Tropical Depression 07W. Tropical Storm Wipha, which formed on July 16 near the Philippine coast, caused widespread damage and fatalities between northern Vietnam and south China. By the end of the month, three tropical cyclones had formed: Francisco, Co-may, and Krosa. Typhoon Co-may affected the Philippine provinces of Pangasinan and Ilocos Sur, the Ryukyu Islands, and eastern China, killing a total of 55 people and causing US$73 million in damage. The month ended with the formation of Tropical Storm Bailu on July 31.
Peak season activity
Two simultaneous tropical cyclones on September 20, typhoons Ragasa (left), and Neoguri (upper right)
August was slightly active compared to the previous month. Early on August 2, Hurricane Iona, which was weakening, entered the basin from the Central Pacific as a tropical depression. Two tropical depressions formed between August 2 and 4, while Typhoon Podul formed on August 6. Podul made landfall in Taiwan as a Category 1 typhoon and then in China as a tropical storm, causing moderate damage there and claiming two lives. Tropical Depression Fabian formed on August 7 and Tropical Depression 17W ten days later. Tropical Storm Lingling formed near Japan on August 17, causing minimal damage, while Typhoon Kajiki, which formed on August 22, caused extensive damage in northern Vietnam after skirting the southern part of Hainan Island, killing a total of 17 people and causing US$501 million in damage. The month ended with the formation of Tropical Storm Nongfa on August 27.[8]
The month of September began with Tropical Storm Peipah on September 2. Typhoon Tapah formed three days later, making landfall in Taishan, Guangdong, China, as a Category 1 typhoon on September 8, killing 12 people. During the peak of the season, three tropical cyclones formed: Mitag, Ragasa, and Neoguri. Typhoon Ragasa became the first super typhoon of the season, as well as the first Category 5 typhoon recorded in the basin, making it the latest Category 5 typhoon since Typhoon Hinnamnor in 2022. Typhoon Neoguri strengthened into a Category 4 tropical cyclone in fresh waters without affecting some areas. Tropical Storm Bualoi formed on September 22 near the Philippines.
On June 5, the JTWC began tracking an area of atmospheric convection located 300km (180mi) west of Yap in the Federated States of Micronesia, noting that the system was in an environment favorable for tropical cyclogenesis.[9] The next day, the JMA noted that it had developed into a low-pressure area.[10] After crossing Luzon, the JMA indicated that the system had strengthened into a tropical depression over the South China Sea on June 9.[11] By 06:00 UTC on June 10, the system was traveling south of the Paracel Islands,[12] and three hours later, the JTWC issued a TCFA and subsequently upgraded it to a tropical depression,[13] assigning it the designation 01W later that day[14] as it moved west-northwestward along the southwestern periphery of a mid-level subtropical high.[15]
The following day, the depression intensified into a tropical storm and was named Wutip by the JMA.[16] At 18:00 UTC, the JMA further upgraded the system to a severe tropical storm.[17] As Wutip approached the subtropical ridge axis later on, it curved northeastward, briefly passed over the far western part of Hainan Island, and made its first landfall near Dongfang City at around 23:00 CST (15:00 UTC) on June 13,[18] before reemerging over the Gulf of Tonkin shortly after.[19] On June 14, the JTWC reported that Wutip had rapidly intensified into a minimal typhoon, although its deep convection had largely collapsed.[20] Later that day, Wutip made its second landfall near Leizhou City in Guangdong Province at around 12:30 CST (04:30 UTC).[21] After landfall, it weakened into a minimal tropical storm, as satellite imagery indicated that its eye had filled in.[22] The JMA downgraded Wutip to a tropical depression on the same day when it was inland, and continued tracking the system until it dissipated at 12:00 UTC on June 15.[23][24]
On June 11, the JMA announced that a tropical depression had developed east of the Philippines.[25] On the same day, the PAGASA started monitoring the disturbance as a low-pressure area while it was still inside the Philippine Area of Responsibility (PAR).[26] By the following day, it had intensified into a tropical depression and was named Auring by the PAGASA.[27] The PAGASA reported that Auring made landfall in Taiwan and later weakened into a remnant low due to the frictional effects of its landfall.[28][29] The agency issued its final advisory when the system exited the PAR,[30] while the JMA continued to monitor it until it was last noted on June 13.[31] The system was not tracked by the JTWC.
On June 12, Taiwan's Central Weather Administration issued a heavy rain warning for the counties of Yilan, Hualien, Taitung, and Pingtung.[32] Heavy rainfall was recorded in Daliao District, with 205.5mm (8.1in) of precipitation recorded.[33] At least one fatality and four injuries were reported due to the system.[34] In China, the depression brought moisture northward along the edge of the Pacific high, resulting in significant rainfall in Zhejiang and Shanghai, with 52.9mm (2.1in) recorded in Shanyang, Shanghai.[35] In the Philippines, Auring brought moderate to heavy rainfall and thunderstorms to the provinces of Batanes and Cagayan.[28]
A tropical depression formed north of the Northern Mariana Islands on June 21.[36] As it continued to develop, the JTWC designated it 02W on the next day.[37] The system was situated in an area of low to moderate wind shear near the tropical upper-tropospheric trough, which limited outflow. Despite this, it still managed to intensify into a tropical storm on June 23, receiving the name Sepat from the JMA.[38] Steered northwest by a subtropical ridge located to its northeast, Sepat strengthened as its structure improved.[39] However, Sepat's convective activity decreased significantly on June 24, halting any intensification.[40] Later that day, the JTWC assessed that Sepat had weakened into a tropical depression as it slowed and entered a drier, more hostile environment.[41] A trough approaching from the west began to impart strong wind shear on the depression as it neared Japan and turned north-northeastward.[42][43] Further affected by colder sea surface temperatures, Sepat initiated its extratropical transition early on June 26, and as a result, the JTWC discontinued all advisories on Sepat.[44]
On June 24, the JMA announced that a tropical depression had developed west of the Philippines. As convective activity increased the next day, the JTWC designated the system as Tropical Depression 03W.[45] Steered by a subtropical ridge located to its northeast, 03W tracked northwestward and remained poorly organized.[46] The depression made landfall on the eastern coast of the Leizhou Peninsula by 02:00 UTC on June 26,[47] moving inland before dissipating that day.[48]
Heavy rains battered Northeastern Vietnam, triggering a landslide in Yên Bái Province which destroyed a house, killing one person inside.[49] In Hainan, 03W brought severe flooding to the regions previously affected by Tropical Storm Wutip, causing widespread damages to crops and roads. Thousands were evacuated as a result, and five people were reported to have died in the flooding.[48]
On July 1, the JMA announced that a new tropical depression had developed near the Northern Mariana Islands.[citation needed] Later that day, the JTWC designated the system as a tropical depression, thereby designating it as 04W.[50] Though its circulation was initially exposed, by July 2 the cyclone had intensified into a tropical storm,[51] and it received the name Mun later that day.[52] Early on July 3, Mun's convection waned as dry air disrupted the cyclone,[53] though it began to recover later that day as deep convection returned.[54][55] Mun later moved through unfavorable conditions, citing dry air environment, weak equatorward outflow aloft, high northeasterly windshear, which helped in degrading back into a tropical storm on July 7.[56] The JTWC would later discontinue warnings with Mun on July 8 as it started to move through cooler waters, making its deep convection collapse.
Early on July 4, convective activity associated with a disturbance located about 550km east-southeast of Hong Kong rapidly consolidated. As a result, the JTWC designated the system as tropical depression 05W, while the PAGASA named it Bising.[57][58] Later that day, the JTWC upgraded the depression to a tropical storm as it began developing a central dense overcast (CDO),[59] and the JMA accordingly named the system Danas.[60] On July 5, the JMA later upgraded Danas into a severe tropical storm as it continued to intensify over favorable conditions south-west of Taiwan. Danas headed north and made landfall at peak intensity near Budai, Chiayi County, Taiwan at 23:40 TST (15:40 UTC) on July 6, making it the first typhoon to make landfall on the western coast of the island since Typhoon Wayne in 1986.[61] After traversing Taiwan, it weakened into a severe tropical storm after its low-level structure got weak and disorganized.[62] The storm further weakened into a tropical storm before making two more landfalls in Dongtou District, Wenzhou and Rui'an on July 8.[63] After landfall, the storm later downgraded into a remnant low as it continued to move inland. The JMA continued to track the system until it issued its last warning on July 10.
Heavy rains from Danas and the southwest monsoon affected 13,006 people across 14 barangays in the Philippines, destroying one house and damaging 12 others, according to the National Disaster Risk Reduction and Management Council (NDRRMC). Twenty-three areas of Central Luzon reported flooding. At least 219 cities and municipalities suspended classes, while 36 suspended work.[64] Two people died from the effects of the storm in Taiwan, while 726 others were injured.[65] One person also died in the Philippines due to flooding caused by the storm.[66]
A disturbance formed 100km west of Iwo Jima on July 11 and was designated 06W by the JTWC. On the same day, the JMA followed suit and designated it as a tropical depression.[citation needed] On July 12, 06W later intensified into a tropical storm, which was named Nari by the JMA. Satellite imagery showed that Nari was partly obscured, with its deep convection developing to the east of the storm's center.[67] Nari was upgraded into a severe tropical storm on July 13 as it continued to strengthen. However, another satellite imagery showed cloud bands spiraling around and getting shallower. Its deep convection also collapsed due to low sea surface temperatures near the edge of the Kuroshio Current.[68] Nari transitioned into an extratropical cyclone on July 15 as it moved east-northeastward towards Hokkaido. At 02:00 that day, the storm made landfall near Cape Erimo at the southern tip of the island, the first time that a tropical cyclone made landfall in the prefecture since Tropical Storm Conson in 2016 and the first on record in July since 1951.[69][70] The storm dissipated on July 15, prompting the JTWC to make its final advisory on that day.
Gusty winds, rough surf, and heavy rainfall were reported. A total of 144mm (5.67in) of rainfall was recorded in Mie Prefecture. Total economic damages caused by the storm exceeded US$1million.[71]
The JTWC noted that a disturbance had developed in the East China Sea 328km east of Shanghai on July 11. Later, the JMA upgraded it to a tropical depression at noon. The next day, the JTWC issued warnings on the system despite being a subtropical depression, designating it 07W. Over the next few days, the storm traveled east and made landfall over Kyushu on July 13 with a pressure of 992 hPa according to the JMA.[citation needed]
On July 15, the JTWC began tracking a low-pressure system off the coast of the Ogasawara Islands. Shortly thereafter, the system's development potential was raised to high, prompting the issuance of a TCFA. Later that day, the JTWC upgraded the disturbance to a tropical depression and designated it as 08W, although the JMA had not yet classified it as such; instead, the agency issued gale warnings for Japan's eastern coast. The system accelerated rapidly northward, reaching a forward speed of 61km/h (38mph) between 15:00 and 21:00 JST, following a track similar to that of Nari.[73][74] After crossing Hokkaido, the JTWC downgraded the system to a remnant low and issued its final advisory the next day.
An area of low pressure formed inside the PAR about 1,040 km (646 mi) east of the Philippines on July 15.[75] By 08:00 PHT (00:00 UTC) on July 16, it developed into a tropical depression and was named Crising by the PAGASA.[76] The JTWC classified it as a monsoon depression due to its large circulation, later issuing a TCFA as convection increased.[77] At 02:00 PHT (18:00 UTC) on July 18, Crising strengthened into a tropical storm, named Wipha by the JMA. The system moved northwest, passing near Santa Ana, Cagayan and the Babuyan Islands as it intensified.[78] The JTWC followed suit and subsequently upgraded it to tropical storm 09W.[citation needed] At 08:00 PHT (00:00 UTC) on July 19, Wipha became a severe tropical storm over the South China Sea.[79] It gradually intensified into a typhoon before making landfall over Taishan in Guangdong Province.[80] Wipha crossed the Gulf of Tonkin and weakened before making a second landfall in Hưng Yên and Ninh Bình provinces, Vietnam, on July 22.[81][82] The JTWC issued its final advisory as the storm weakened inland. Wipha dissipated on July 23. Its remnants later redeveloped over the North Indian Ocean into BOB 04, which dissipated on July 27.
Wipha enhanced the southwest monsoon, triggering floods in the Philippines[83] and affecting over 9.5million people.[84] 40 fatalities, 33 injuries, and eight people missing were reported.[85] In Hong Kong, the HKO raised Hurricane Signal No.10, its highest warning level.[86] At least 33 people were injured, 711 trees were reported downed, and 277 people were evacuated.[87]
On July 21, the JTWC first noted a low-pressure area south-southwest of Kadena Air Base. The following day, the JMA classified the system as a tropical depression. The JTWC and PAGASA later did the same, with the PAGASA assigning the local name Dante and the JTWC designating it as Tropical Depression 10W after initially issuing a TCFA.[88][89] On July 23, the JMA, the JTWC, and the PAGASA upgraded the system to a tropical storm, naming it Francisco, as it tracked north-northwestward.[90]
The storm was steered by the pressure gradient between a subtropical ridge to the north and a monsoon gyre to the south. Satellite imagery showed a burst of deep convection over the storm's LLCC, briefly causing a northward wobble in its track as the vortex aligned beneath the convective canopy.[91] Francisco subsequently turned westward towards northern Taiwan Strait, where dry mid-level air and weak outflow caused it to weaken back to a tropical depression, and then to a remnant low the following day.[92]
Heavy rain and tropical-storm-force winds were reported in the Ryukyu Islands.[93]
On July 23, a weak low-pressure area formed northeast of Ilocos Norte.[94] It quickly organized over the West Philippine Sea, prompting a TCFA from the JTWC. Soon after, the JTWC, the PAGASA, and the JMA classified it as a tropical depression, with the PAGASA naming it Emong and the JTWC designating it 11W. It later intensified into a tropical storm,[95] named Co-may by the JMA. Due to an imminent Fujiwhara effect with Francisco, Co-may looped northeast towards the Ilocos Region.[96] On July 24, all[which?] agencies upgraded it to a minimal typhoon.[97] At 22:40 PHT (06:40 UTC), Co-may made landfall in Agno, Pangasinan, the strongest to hit the province in 16 years, and weakened into a severe tropical storm.[98][99] It made a second landfall in Candon, Ilocos Sur early July 25 and weakened while crossing the Cordilleras.[100] It continued weakening over the Babuyan Channel[101] and was downgraded to a depression before passing through the Ryukyu Islands.[102] Co-may re-strengthened near Okinawa on July 27, then struck Zhujiajian Island, Zhejiang on July 29 and Fengxian, Shanghai on July 30. It became a remnant low on July 31[citation needed] and dissipated on August 3 after crossing Yancheng.
On July 21, the JTWC began monitoring a disturbance that had formed near Guam under marginally favorable environmental conditions. The system slowly consolidated over the following days. On July 23, the JTWC issued a TCFA for the system, and a few hours later, it was designated as Tropical Depression 12W. The following day, the JMA assigned the system the name Krosa. As its convection began to organize, the JMA upgraded Krosa to severe tropical storm intensity. On July 27, the JMA upgraded Krosa to a typhoon, with JTWC later following suit; however, it weakened into a severe tropical storm on July 28 and then further weakened into a tropical storm on July 30, and then re-strengthed into severe tropical storm on the following day.[109] Krosa maintained its strength due to marginally favorable environmental conditions despite its fully exposed, ragged LLCC.[110] Krosa deteriorated back again into a tropical storm for the second time on August 3 due to increasing vertical wind shear with cooler[how?] waters. On August 4, Krosa would undergo extratropical transition as it crossed into the baroclinic zone to the north.
A tropical depression developed southeast of Okinawa Island on July 31. On August 1, the JTWC issued a TCFA for the system, citing the potential for tropical cyclogenesis in the coming days. By the next day, the JTWC designated the system as Tropical Depression 13W. In the early hours of August 3, both the JMA and the JTWC upgraded 13W to a tropical storm, with the former assigning the name Bailu.[111] Satellite imagery at the time indicated a slowly consolidating LLCC, although the system remained asymmetric. Several smaller vortices were observed merging, accompanied by intermittent convection along the storm's periphery. Bailu was embedded in a marginally favorable environment, characterized by elevated atmospheric moisture, warm sea surface temperatures of 27–28°C (81–82°F), low vertical wind shear (5–10knots), and moderate poleward outflow.[112] However, as Bailu turned eastward, it struggled to sustain convection due to less favorable environmental conditions, weakening into a tropical depression on August 4. By August 6, the system had transitioned into an extratropical low after crossing the baroclinic zone and tracking east-northeastward. Shortwave infrared imagery confirmed the completion of its extratropical transition, with wind speeds dropping below 45km/h (24kn) as the process concluded.
The weakening Hurricane Iona, which had originated in, and traversed the Central Pacific basin since July 24, crossed the International Date Line early on August 2 as a tropical depression.[113] Upon entering the Western Pacific basin, both the JMA and the JTWC started monitoring the system and began issuing advisories accordingly. As Iona moved into the new basin, it continued to weaken due to the presence of a dry air mass and persistent vertical wind shear, which hindered any chances of re-intensification. As a result, the JTWC quickly discontinued its warnings shortly after that. However, the JMA continued to track the system's remnants, issuing occasional updates until it was last noted on August 4.[114]
A tropical depression formed north of Wake Island on August 2.[115] Two days later, the JTWC gave it a high chance of development and issued a TCFA, indicating a fully exposed LLCC that is slowly but steadily intensifying despite being in a marginal environment. Later that day, the system was designated as 14W by the JTWC, as they upgraded it to a tropical depression.[116] Satellite derived imagery indicated that 14W's environment was unfavorable for further development, with strong northeasterly shear and dry air present in the Pacific Ocean as the system's structure unraveled. The system dissipated late on August 4 and merged with another disturbance just southwest of Wake Island.[117]
The JMA recognized a tropical depression that formed northwest of Wake Island late on August 4, to the south of the remnants of 14W.[117] Initially, according to the agency, the system only had a low chance of development due to the surrounding marginal environment. However, its chances increased the following day as it continued to slightly organize despite its current environment. Early on August 6, the JTWC followed suit, designating the depression 15W. The system then proceeded to move northward as dry air impinged from the north and west. Under strong easterly flow and high wind shear of 35–45km/h (20–25knots) from the northeast continued eroding the vertical structure of the circulation.[118] 15W dissipated hours later on the same day as the circulation became even more stretched out.[119]
On August 6, the JTWC began monitoring a convective area 230 nautical miles (430km) northeast of Saipan, which was later classified as a tropical depression by the JMA. The JTWC issued a TCFA the following day[120] and designated it as 16W.[121] The system was upgraded to a tropical storm and named Podul by the JMA on August 8.[122] Despite initial disruption from northeasterly vertical wind shear, Podul gradually organized,[123] and the JMA upgraded it to a typhoon on August 9. That same day, it entered the PAR and was named Gorio by the PAGASA.[124] The JTWC followed suit, upgrading Podul to a typhoon later that day, citing improved convective structure despite dry air intrusion.[125] On August 13, Podul made landfall in Taimali, Taitung County in Taiwan at 13:00 TST (05:00 UTC) as a Category2-equivalent typhoon.[126] Podul then crossed through the Central Mountain Range, weakening significantly before it emerged over the Taiwan Strait. The storm made a second landfall in Zhangpu, Fujian Province at 01:00 CST (17:00 UTC) before weakening inland.[127]
In Taiwan, Podul left one person missing, 112 injured, and displaced 8,024 residents.[128] A man in Kaohsiung was killed after falling while repairing a storm-damaged roof.[129] At Taoyuan International Airport, a UPS AirlinesBoeing 747 suffered an engine pod strike while landing amid wind shear, prompting a temporary closure of the north runway for repairs and debris removal.[130] The typhoon also brought heavy rainfall to parts of Southern China after its second landfall.
On August 7, the JTWC identified an area of low pressure east of the Philippine island of Luzon. It then crossed through northern Luzon before the JMA began monitoring the system as a tropical depression on the following day. At 08:00 PHT (00:00 UTC), the PAGASA likewise upgraded the system to a tropical depression and named it Fabian.[131] However, on August 9, the PAGASA eventually downgraded the system to a low-pressure area as persistent vertical wind shear prevented further development and caused its cloud tops to dissipate despite warm sea surface temperatures.[132]
On August 16, Vietnam's National Center for Hydro-Meteorological Forecasting (NCHMF),[133][134] the China Meteorological Administration (CMA),[citation needed] and the Hong Kong Observatory (HKO)[135] reported the formation of a tropical depression over the South China Sea.[a] The NCHMF issued its first warning at 20:00 ICT (13:00 UTC), followed by the HKO at 21:30 HKT (13:30 UTC).[136] At 21:00 MST (13:00 UTC) and 22:20 HKT (14:20 UTC), Macau's Meteorological and Geophysical Bureau (SMG)[137][138][139][140][141] and the HKO both issued Standby Signal No.1.[142] The HKO later replaced this with the Strong Monsoon Signal at 20:20 HKT (12:20 UTC) on August 17,[143] whereas the SMG upgraded to Strong Wind Signal No.3 at 12:00 MST (04:00 UTC) the same day.[144][145] The JMA also began monitoring the system on August 17. The JTWC later classified the system as a monsoon depression, noting its broad circulation with stronger winds on the eastern side and a poorly defined center. On August 18, the agency issued a TCFA, citing favorable conditions in the Gulf of Tonkin,[146] and later upgraded the disturbance to a tropical depression and designating it 17W. That evening, 17W made landfall over Quảng Ninh, Vietnam, before weakening inland; the JTWC issued its final advisory the following day.
In Hong Kong, a Red Rainstorm Warning Signal was issued during the early hours of August 18, prompting the Education Bureau to suspend morning and full-day classes across the territory.
On August 16, the JTWC began monitoring an area of convection about 305 nautical miles (565km) southeast[where?] of Kadena Air Base, noting marginal potential for tropical cyclogenesis.[147] The JMA classified the system as a tropical depression the next day,[148] followed by the PAGASA at 02:00 PHT (18:00 UTC) on August 18, assigning the local name Huaning.[149] Later that day, the JTWC issued a TCFA, citing a consolidating LLCC within a reverse-oriented monsoon trough.[150] Despite initial hindrance from wind shear and dry air,[151] Lingling gradually organized and was designated as 18W by the JTWC at 06:00 UTC. It was upgraded to a tropical storm on August 20[152] and named Lingling by the JMA on August 21. Satellite imagery showed improved convective banding wrapping around a compact LLCC under favorable conditions, including strong outflow, low to moderate shear, and warm 29–30°C (84–86°F)sea surface temperatures.[153] Lingling made landfall near Hioki, Kagoshima at 17:00 JST (08:00 UTC) before weakening into a tropical depression,[154] and later dissipated into a remnant low on August 23.
Although Lingling did not directly strike the Philippines, classes were suspended in parts of Cavite and Cebu due to heavy rainfall enhanced by the storm and the southwest monsoon.[155]Shinkansen services in Kyushu were suspended due to heavy rains caused by Lingling. 95 mm (3.74 in) of rain was observed in Minamikyūshū in Kagoshima Prefecture as the storm neared the city. 300 mm (11.8 in) of rain was also recorded in Southern Kyushu in the morning of August 22. A landslide warning was issued throughout the city, with at least five landslides reported through Ichikikushikino. Flood alerts were also issued at Minamisatsuma and Minamikyushu. Residents from low-lying areas were forced to evacuate as Lingling made landfall over the area. Streets in affected regions quickly became waterlogged, while public transport services faced significant delays.
On August 20, a low-pressure area entered the PAR east of southeastern Luzon.[156] It was upgraded by the PAGASA to Tropical Depression Isang on August 22 near Aurora,[157] with the JMA and the JTWC issuing similar classifications.[158] Isang made landfall over Casiguran, Aurora that morning,[159] and was later designated as 19W by the JTWC as it entered the West Philippine Sea.[160] By August 23, the system started to intensify in the South China Sea under favorable conditions,[161][162] becoming a tropical storm and named Kajiki at 01:05 UTC.[163] Despite moderate wind shear, Kajiki reached severe tropical storm strength by 12:50 UTC[163] and was later upgraded to a typhoon by the JTWC.[164] As Kajiki neared Sanya, it strengthened into a Category2-equivalent typhoon with a 23-nautical-mile-wide (43km) eye.[165][166] It then weakened slightly over the Gulf of Tonkin due to lower ocean heat content,[167] undergoing an eyewall replacement cycle while maintaining strong outflow.[168][169] Kajiki made landfall between Nghệ An and Hà Tĩnh around 18:00 ICT (11:00 UTC) on August 25. The storm later moved inland, rapidly deteriorating until it reportedly dissipated on the following day.
The storm, along with the southwest monsoon,[b] affected more than 50,000 people and displaced more than 25,000 across the Philippines[170] and caused extensive flooding in Metro Manila.[171] In Vietnam, Kajiki caused at least four deaths and injured 47 people.[172] The storm damaged over 34,700 homes, 380 schools, and 44 health facilities, and affected 116,700ha (288,000 acres) of crops. The remnants of Kajiki caused deadly floods and landslides in Northern Thailand, killing seven and injuring 24 in Mae Suek, Chiang Mai, with two people missing and dozens of homes damaged.[173][174] Flooding also struck Mae Chaem and Mae Hong Son, while in Myanmar, Kajiki's remnants caused flash floods in Tatkon Township, prompting evacuations,[175] and a landslide in Pinlaung Township, Shan State.[176]
On August 23, the PAGASA began tracking a weather system that originated from an area of low pressure just east of Surigao del Sur on Mindanao.[177][178][179] On August 27, the JMA starting monitoring the same system, identifying it as a tropical depression located approximately 106 nautical miles (196km) off the northwestern coast of Luzon. However, six hours later, the JMA downgraded the system back to a low-pressure area. This decision was later reversed in their next weather advisory bulletin, where the system was once again classified as a tropical depression.[citation needed] On August 28, the PAGASA also upgraded the disturbance to a tropical depression, assigning it the local name Jacinto, the replacement name for Jolina.[8] The JTWC subsequently issued a TCFA and initially classified the system as a monsoon depression. A few hours later, the JTWC reclassified it as a tropical depression and designated it as 20W as it moved westward.[180] 20W then moved into the South China Sea under a marginally favorable environment, characterized by northerly to northeasterly upper-level flow that slightly hindered development.[181] Satellite imagery also depicted a partially exposed LLCC, with disorganized convection flaring over the southern quadrant.[181] On August 30, 20W was upgraded to a tropical storm and assigned the name Nongfa by the JMA, accompanied by vigorous convection with deep, cold cloud tops and tightening rainbands, indicating a mature structure.[182] Nongfa made landfall between the provinces of Quảng Trị and Hà Tĩnh at 15:30 ICT (08:30 UTC).[183] The storm later interacted with land, moving westward through mountainous terrains in Vietnam and Laos. Both agencies issued their final advisories on August 31 as the system weakened into a remnant trough[citation needed]. The remnants of Nongfa later crossed into the Bay of Bengal but did not redevelop, as it remained over the basin only briefly before making landfall in West Bengal, India. On September 6, a new low pressure area associated with the remnant energy of Nongfa redeveloped over the Arabian Sea into Deep Depression LAND 04.
The PAGASA issued heavy rainfall warnings due to the combined effects of the low-pressure area and the southwest monsoon.[b][184][185] On August 28, the HKO issued Standby Signal No.1 at 19:10 HKT (11:10 UTC)[186] and Macau's SMG issued the same signal at 19:00 MST (11:00 UTC).[187][188] All signals were cancelled and was replaced with Strong Monsoon Signal for the respective territories at 18:10 HKT (10:10 UTC)[189][190][191] and 16:30 MST (08:30 UTC) on August 29.[192][193]
Nongfa brought heavy rainfall to Central Vietnam, cutting off roads and isolating dozens of mountain villages as it made landfall between the provinces of Quảng Trị and Hà Tĩnh. In Hà Tĩnh, flooding submerged roads in Hương Khê District, forcing closures along National Highway 15. In the district's Phúc Trạch commune, 46 households belonging to the Chứt ethnic minority were cut off, while flooding on Trần Phú Street in Hương Khê left cars and motorbikes underwater. Officials noted that incomplete drainage systems worsened the impact.
In Nghệ An, authorities banned all sea activities by August 30, and all fishing boats were ordered back to shore. Provincial authorities in Quảng Trị convened emergency meetings on August 29 to coordinate evacuation and storm response, according to Trần Phong, Chairman of the Quảng Trị Provincial People's Committee.[194] 57 households (165 people) were evacuated by the local authorities from Hướng Lập, Bến Quan, and Hiền Giang communes to safe shelters. Ahead of National Day celebrations on September 2, officials reinforced safety measures, installed barriers, and deployed personnel for continuous monitoring in high-risk areas. Heavy rainfall triggered multiple landslides in mountainous areas, while subsidence and partial road collapses occurred as heavy vehicles attempted to cross waterlogged routes. Military, police, and border guard units were mobilized to clear debris and restore key transportation links. By August 31, 8,677 vessels carrying 23,947 workers had taken shelter in the province, though 48 boats with 251 fishermen remained at sea but maintained communication. 52 large and medium-sized reservoirs were at 65% of capacity and remained operational. However, the Tả Kiện Giang dyke overflowed, inundating rice fields; reports indicated that about 690 hectares (1,700 acres) of summer–autumn rice and 65.5 hectares (162 acres) of vegetables were damaged.
On September 3, Prasert Jantararuangtong, Deputy Prime Minister of Thailand and Minister of the Digital Economy and Society, expressed concern over water conditions in areas affected by Nongfa and the prevailing monsoon trough. Heavy rainfall impacted the Pa Sak, Yom, and Nan river basins, with severe flash floods reported in Phetchabun Province. Flooding damaged homes and farmland in Lom Kao, Nam Nao, Lom Sak, Mueang Phetchabun, and Nong Phai districts, prompting evacuations and the relocation of belongings to higher ground as floodwaters began to recede towards the Pa Sak Jolasid Dam. In Phitsanulok, rising water levels in the Nan River were linked to heavy rainfall near the Sirikit Dam. To mitigate downstream impacts, the dam reduced its water discharge. Similarly, the Mae Mok Dam exceeded its storage capacity, releasing excess water into the Yom River basin. The Deputy Prime Minister instructed the National Water Resources Office (NWRO) to establish temporary water management centers in the affected basins. These centers were tasked with ensuring proper water flow, coordinating assistance, and minimizing flood impacts.[195]
Although Peipah did not directly impact the Philippines, its interaction with the southwest monsoon affected over 93,000 people and displaced nearly 1,300 across four regions.[206] In Kantō, Kōshin'etsu, and Tōkai, Peipah caused major transport disruptions, including delays and cancellations on the Tōkaidō Shinkansen and at Narita and Haneda.[207] In Shizuoka Prefecture, strong winds damaged or destroyed dozens of houses and injured at least 24 people. In Yaizu, a greenhouse collapse seriously injured a farmer.[208][209] Flooding was reported in Kamakura.[210] A tornado and severe winds injured several people and left about 17,000 households without power. Both the Tōkaidō and San'yō Shinkansen lines were suspended.[211]
On September 4, the JTWC began tracking a low-pressure area that developed west-southwest of Vigan, Ilocos Sur, citing favorable conditions for tropical cyclogenesis despite a poorly defined LLCC.[212] On September 5, the NCHMF reported the formation of a tropical depression over the South China Sea in their first warning bulletin, issued at 21:00 ICT (14:00 UTC).[213] At 02:00 PHT on September 6 (18:00 UTC), the PAGASA upgraded the disturbance to a tropical depression, assigning it the local name Lannie.[214] The JTWC issued a TCFA later that same day, citing a high chance of further development.[215] Around 09:00 UTC, the JTWC subsequently upgraded the system to a tropical depression, designating it as 22W.[216]At 21:00 JST (12:00 UTC), the JMA upgraded the system to a tropical storm,[citation needed] naming it Tapah, with JTWC following suit three hours later.[217] Satellite imagery showed that Tapah had a partially exposed LLCC, with deep convection organizing over the center as it tracked northwestward.[218] The JMA then upgraded it into a severe tropical storm early on September 8, before it made its first landfall over the Chuanshan Archipelago at 23:00 UTC.[219] As it moved north-northwestwards, Tapah then rapidly intensified into a Category 1-equivalent typhoon before it made its final landfall over Taishan, Guangdong at 00:00 UTC.[219] Both agencies made their last warning afterwards as the typhoon interacted with the rugged terrain over Southern China, causing it to rapidly dissipate.[219]
Tapah caused 12 injuries in Hong Kong and generated minor flooding in Macau.[220]
On September 15, the JTWC identified a low-pressure area 90 nautical miles (167km) east-northeast of Legazpi, Albay, in a favorable environment with warm 30°C (86°F) sea surface temperatures, low 10–15 knots (19–28km/h; 12–17mph) wind shear, and moderate outflow.[221] The next day, the JMA classified the system as a tropical depression at 15:00 JST (06:00 UTC),[222][223] and PAGASA named it Mirasol at 14:00 PHT.[224] The JTWC issued a Tropical Cyclone Formation Alert at 03:30 UTC,[225] and later upgraded the system to 23W at 09:00 UTC.[226] The HKO also reported its development.[227][228] Mirasol made landfall over Casiguran, Aurora at 03:20 PHT on September 17.[229] It weakened over the Cordillera Central before re-emerging into the West Philippine Sea.[230][231] At 15:00 JST on September 18, the JMA upgraded the system to Tropical Storm Mitag.[232] Mitag intensified over the South China Sea but later encountered dry air and land interaction, prompting the JTWC to issue its final advisory.[233][234] Mitag made landfall near Shanwei, Guangdong and was later downgraded to a tropical depression by the JMA.[235] The JMA later made its final warning at 21:00 JST (12:00 UTC) of September 20 as it dissipated.
On September 17, the HKO issued Standby Signal No. 1 at 21:20 HKT (13:20 UTC),[236] followed by Macau's SMG at 00:00 MST (16:00 UTC) on September 18.[237] Both agencies upgraded to Signal No. 3 on September 19 as Mitag approached.[238][239] The SMG cancelled all signals at 06:00 MST (22:00 UTC) on September 20,[240] while HKO lowered to Signal No. 1 at 09:20 HKT (01:20 UTC) and canceled all warnings an hour later.[241]
Mitag caused flooding in the Philippines, killing three people and leaving four missing in Valencia, Bukidnon.[242]
On September 16, the Joint Typhoon Warning Center (JTWC) identified a tropical disturbance located approximately 333 nautical miles (617km) north of Yap.[243] Favorable environmental conditions supported gradual development, and the Japan Meteorological Agency (JMA) classified the system as a tropical depression the following day.[244] Upon entering the Philippine Area of Responsibility (PAR) on September 17, the depression was named Nando by PAGASA.[245] The system strengthened over the Philippine Sea, attaining tropical storm intensity on September 19, at which point it was assigned the international name Ragasa by the JMA and designated 24W by the JTWC.[232][246] Benefiting from favorable outflow and warm sea surface temperatures, Ragasa underwent rapid intensification and reached typhoon strength by September 20.[247] On September 21, both PAGASA and the JTWC upgraded Ragasa to a super typhoon. The JTWC estimated 1-minute sustained winds of 270 km/h (165 mph)—equivalent to a Category 5 super typhoon—with a minimum central pressure of 910hPa (26.87inHg).[248][249] The JMA classified Ragasa as a violent typhoon, assessing ten-minute sustained winds of 205 km/h (125 mph) and a central pressure of 905hPa (26.72inHg).[250] At peak intensity, Ragasa made landfall over Panuitan Island in Calayan, Cagayan at approximately 15:00 PHT (07:00 UTC) on September 22.[251] Following landfall, the typhoon began to weaken gradually, undergoing an eyewall replacement cycle that produced a 25-nautical-mile-wide (46km; 29mi) eye as it tracked west-northwestward toward the South China Sea.[252] At 17:00 CST on September 24, Ragasa made landfall over Hailing Island in Yangjiang, Guangdong Province in China.[253] At 14:00 UTC the JTWC issued its final warning on Ragasa.[254] Ragasa made a third[clarification needed] landfall in Beihai, Guangxi on the morning of September 25 as a tropical storm.[255] At 12:00 ICT (05:00 UTC), the Vietnamese National Center for Hydro-Meteorological Forecasting considered Ragasa to have made landfall over Quảng Ninh province in Vietnam as a tropical depression.[256]
Ragasa caused damage across parts of the Philippines, resulting in at least 11 deaths and 11 injuries.[257][258] In Taiwan, the system produced flooding that killed at least 14 people, injured 54 others, and left 11 missing from the bursting of the Matai'an Creek Barrier Lake.[259][260] At least 101 people were injured in Hong Kong.[261]
On September 17, the Joint Typhoon Warning Center (JTWC) identified an area of convection located approximately 219 nautical miles (406km) north of Wake Island, with multispectral imagery revealing an ill-defined low-level circulation center (LLCC) and flaring convection along the system's western periphery.[262] Later that day, the Japan Meteorological Agency (JMA) began issuing bulletins on the disturbance, classifying it as a tropical depression at 21:00 JST (12:00 UTC).[263] At 22:20 JST (13:20 UTC), the JMA upgraded the depression to a tropical storm, assigning the name Neoguri.[232] By 12:00 JST (03:00 UTC) on September 19, the JMA further upgraded Neoguri to a severe tropical storm, supported by favorable environmental conditions and warm 29–30°C (84–86°F) sea surface temperatures.[264] Satellite imagery depicted curved convective banding wrapping around the obscured LLCC, with a well-defined microwave eye feature also becoming evident.[265] Both the JMA and the JTWC upgraded Neoguri to a minimal typhoon early on September 20, as low-level cloud lines continued to wrap tightly beneath the storm's main convective canopy.[266] The JTWC additionally reported persistent convective bursts consolidating around a ragged eye feature, indicative of rapid intensification as the cyclone tracked west-northwestward.[267] At 09:00 UTC on September 20, the JTWC upgraded Neoguri to a Category 2-equivalent typhoon, with satellite data indicating a compact and tightly wrapped core, alongside the development of a ragged eye over the preceding six hours.[268] Shortly thereafter, the JMA upgraded the cyclone to the season's first "very strong" typhoon at 18:00 JST (09:00 UTC).[269] Owing to low wind shear and continued warm waters, Neoguri intensified explosively, with maximum sustained winds rising by 55 knots (102km/h; 63mph) within 24 hours.[270] A large, axisymmetric eye became increasingly distinct, with satellite-derived infrared measurements showing a temperature of 19°C (66°F), further confirming the cyclone's structural maturity and intensity.[270] On September 21 at 09:00 JST, the JMA classified Neoguri as a violent typhoon, with a minimum central pressure of 920hPa (27.17inHg).[271] The storm subsequently reached its peak intensity as a Category 4-equivalent typhoon, with 1-minute sustained winds of 230 km/h (145 mph) and a central pressure of 936hPa (27.64inHg).[272] Around this time, the cyclone slowed and began curving northwestward.[272] Significant weakening commenced by 15:00 UTC on September 21, as satellite imagery depicted rapidly cycling convective bursts and an increasingly obscured eye while the system drifted north-northwestward.[273] Neoguri continued shifting northward as a mid-latitude shortwave trough began interacting with its western flank.[274] Warming cloud tops, upwelling, and increasing vertical wind shear further hindered the cyclone's organization.[275] Subsequent satellite analyses revealed a highly asymmetric system, with persistent 20–25 kt southwesterly shear disrupting deep convection as Neoguri tracked east-northeastward. An upper-level trough located to the northwest enhanced poleward outflow but also imposed increasingly hostile conditions, accelerating structural decay. The JTWC downgraded Neoguri to a tropical storm on September 24.[276] The JTWC upgraded Neoguri back to a typhoon later that day.[277]
On September 22, the JTWC began tracking an area of convection that had developed approximately 82 nautical miles (152km) northeast of Yap. Multispectral satellite imagery showed a disorganized, broad area of flaring convection with moderate low-level convergence along its northwestern periphery. At that time, the disturbance was situated in a marginal environment, with high vertical wind shear of 20–25 knots (37–46km/h; 23–29mph), moderate poleward outflow, and warm sea surface temperatures.[278] The following day, at 03:00 JST (18:00 UTC), the JMA also began issuing advisories on the same system, classifying it as a tropical depression.[279] The disturbance later became better organized in a more favorable environment, and the JTWC issued a TCFA at 02:00 UTC, citing a high chance of development.[280] The system entered the PAR at 16:00 PHT (08:00 UTC) and was given the local name Opong by PAGASA.[281] Early on September 24, the JTWC designated the system as 26W, while the JMA named it Bualoi at 03:00 JST (18:00 UTC).[282] The JTWC later upgraded it to a tropical storm, noting increasingly organized deep convective banding over the northwestern and southern quadrants of the LLCC.[283] Later that day, PAGASA and the JMA upgraded the system as a severe tropical storm.[284] On September 25, at 11:30 PST (15:30 UTC), Bualoi made landfall over San Policarpo, Eastern Samar as a typhoon.[285][286] PAGASA later downgraded Bualoi into a severe tropical storm before it made another landfall over Palanas, Masbate at around 04:00 PHT (20:00 UTC) of the following day.[287] Bualoi made four other landfalls as it traversed across Mimaropa later that day, bringing the total number of landfalls to six: the others were at Milagros, Masbate (05:30 PHT; 21:30 UTC), San Fernando, Romblon (08:10 PHT; 00:10 UTC), Alcantara, Romblon (09:20 PHT; 01:20 UTC) and Mansalay, Oriental Mindoro (11:30 PHT; 03:30 UTC).[288] Afterwards, it reemerged over the Mindoro Strait.[289]
Bualoi caused damage in parts of the Philippines and left 10 people dead and another 10 missing.[290] More than 87,000 people were displaced.[291]
Other systems
A tropical depression active on February11.
On February 11, the JMA noted that a tropical depression had formed west of the Philippines, 305km (165nmi; 190mi) southwest of Kalayaan, Palawan.[292][293] The next day, the JTWC began tracking the system around 267 nautical miles (494km) west-northwest of the Spratly Islands,[where?] noting that it was in an unfavorable environment for development, with significant wind shear of 25–30mph (35–45km/h) and marginal sea surface temperatures (SSTs) of 26°C (79°F).[294] As a result, the JTWC stopped tracking the system the next day, noting that it had dissipated.[295] The JMA kept tracking the depression until it dissipated on February 15.[296] Although it regenerated the next day,[297] the JMA stopped tracking it by February 17.[298] Alongside a low-pressure trough passing through Vietnam, rains from the depression caused several regions in the southeastern parts of the nation to break unseasonal rain records for the month of February, with Ho Chi Minh City recording its heaviest rainfall in the past twenty years. In the town of Long Thành, 175mm (6.9in) was recorded.[299] Some towns, like Nhà Bè, saw their highest rainfall in 41 years.[300] On Hòn Đốc island, rainfall reached 128.2mm (5.05in) in the early morning of February 16, highest in the Mekong Delta on record.[301] Additionally, Puerto Princesa and other parts of Palawan saw severe flooding due to rains from the system, a shear line, and the intertropical convergence zone.[293]
On July 30, the JTWC marked a subtropical depression east of Japan and designated it Invest 92W. It dissipated a few hours later without being recognized by the JMA.
On August 1, the JMA noted that a tropical depression had formed on Gulf of Tonkin. Several hours later, it was removed from the JMA's weather forecast map. However, later that day, the system was reclassified as a tropical depression again, but it was short-lived and dissipated on the following day.
On August 13, the JTWC marked a subtropical depression near the International Date Line and designated it Invest 99W. It dissipated on August 14 without being recognized by the JMA.
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.[302] 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 65km/h (40mph).[303] The PAGASA name 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.[302] The names of significant tropical cyclones are retired, by both the PAGASA and the Typhoon Committee.[303] 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 the PAGASA and the Typhoon Committee in the spring of 2026.[303]
A tropical cyclone is named when it is judged to have 10-minute sustained wind speeds of 65km/h (40mph).[304] 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.[305] Retired names, if any, will be announced by the WMO in 2026, though replacement names will be announced in 2027. The next 28names on the naming list are listed here along with their international numeric designation, if they are used. All the names in the list are the same, except for Co-may, Nongfa, Ragasa, Koto and Nokaen, which replaced Lekima, Faxai, Hagibis,Kammuri, and Phanfone respectively after the 2019 season. The names Co-may, Nongfa, and Ragasa were used for the first time this season.
The PAGASA uses its own naming scheme for storms that develop in or enter their self-defined area of responsibility.[306] During this season, the PAGASA is using the following list of names, that was last used during 2021 and will be used again in 2029, updated with replacements of retired names, if any.[306] All of the names are the same as in 2021 except Jacinto, Mirasol and Opong, which replaced the names Jolina, Maring and Odette after they were retired.[306] All three names were used for the first time this season.
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 2025. The tables also provide an overview of a system's intensity, duration, land areas affected, and any deaths or damages associated with the system.
1 2 A super typhoon is an unofficial category used by the Joint Typhoon Warning Center (JTWC) for a typhoon with winds of at least 240km/h (150mph).[2]
↑ The Joint Typhoon Warning Center is a joint United States Navy– United States Air Force task force that issues tropical cyclone warnings for western Pacific Ocean and other regions.[3]
↑ Plus 01C; 07W is a subtropical depression according to the Joint Typhoon Warning Center.
↑ The system is recognized by the Joint Typhoon Warning Center only.
↑ Vietnamese: Biển Đông, literally meaning the East Sea
↑ Frequently Asked Questions (Report). Joint Typhoon Warning Center. August 13, 2012. Archived from the original on October 4, 2013. Retrieved September 22, 2012.
↑ Warning and Summary 050600 (Report). Tokyo, Japan: Japan Meteorological Agency. June 5, 2025. Archived from the original on June 5, 2025. Retrieved June 5, 2025.
↑ Warning and Summary 091200 (Report). Tokyo, Japan: Japan Meteorological Agency. June 9, 2025. Archived from the original on June 9, 2025. Retrieved June 9, 2025.
↑ Warning and Summary 051200 (Report). Tokyo, Japan: Japan Meteorological Agency. June 15, 2025. Archived from the original on June 15, 2025. Retrieved June 15, 2025.
↑ Warning and Summary 110600 (Report). Tokyo, Japan: Japan Meteorological Agency. June 11, 2025. Archived from the original on June 11, 2025. Retrieved June 11, 2025.
↑ Warning and Summary 131200 (Report). Tokyo, Japan: Japan Meteorological Agency. June 13, 2025. Archived from the original on June 13, 2025. Retrieved June 13, 2025.
↑ 中央通訊社 (June 13, 2025). "逢甲大學老榕樹倒下 1學生送醫搶救不治 | 社會"[An old banyan tree fell down at Feng Chia University, and one student died after being sent to hospital]. 中央社 CNA (in Chinese). Retrieved June 13, 2025.
↑ "上海这雨何时是个头？明天降水较弱，下周有2-3天间歇期_浦江头条_澎湃新闻-The Paper"[When will the rain in Shanghai end? The precipitation will be weak tomorrow, and there will be a 2-3 day break next week]. www.thepaper.cn. Retrieved June 14, 2025.
↑ Warning and Summary 211200 (Report). Tokyo, Japan: Japan Meteorological Agency. June 21, 2025. Archived from the original on June 21, 2025. Retrieved June 21, 2025.
↑ Warning and Summary 041800 (Report). Tokyo, Japan: Japan Meteorological Agency. July 4, 2025. Retrieved July 4, 2025.
↑ "颱風丹娜絲6日深夜 登陸嘉義布袋"[Typhoon Danas landed in Budai, Chiayi, late at night on the 6th] (in Chinese). Central News Agency. July 6, 2025. Retrieved July 6, 2025.
↑ Warning and Summary 111200 (Report). Tokyo, Japan: Japan Meteorological Agency. February 11, 2025. Archived from the original on February 11, 2025. Retrieved February 11, 2025.
↑ Warning and Summary 160000 (Report). Tokyo, Japan: Japan Meteorological Agency. February 16, 2025. Archived from the original on February 16, 2025. Retrieved February 16, 2025.
↑ Warning and Summary 161200 (Report). Tokyo, Japan: Japan Meteorological Agency. February 16, 2025. Archived from the original on February 16, 2025. Retrieved February 16, 2025.
↑ Warning and Summary 170600 (Report). Tokyo, Japan: Japan Meteorological Agency. February 17, 2025. Archived from the original on February 17, 2025. Retrieved February 19, 2025.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
