This article may be too long to read and navigate comfortably. Consider splitting content into sub-articles, condensing it, or adding subheadings. Please discuss this issue on the article's talk page.(November 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 north of the equator between 100°E and the 180th meridian. Within the northwestern Pacific Ocean, two separate agencies assign names to tropical cyclones, which can result in a system having two names. The Japan Meteorological Agency(JMA)[nb 2] names a tropical cyclone when it is estimated to have 10-minute sustained winds of at least 65km/h (40mph) anywhere in the basin. The Philippine Atmospheric, Geophysical and Astronomical Services Administration(PAGASA) assigns names to tropical cyclones that move into or form as a tropical depression within the Philippine Area of Responsibility (PAR), defined as the area between 135°E–115°E and 5°N–25°N, regardless of whether the JMA has already named the system. Tropical depressions monitored by the United States Joint Typhoon Warning Center(JTWC)[nb 3] are given a numerical designation with a "W" suffix, which means "west", a reference to the western Pacific region.[nb 1]
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, Vietnam's National Center for Hydro-Meteorological Forecasting (NCHMF) and Taiwan's Central Weather Administration (CWA).
On May 7, 2025, 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 prediction of the accumulated cyclone energy (ACE) index due to the lower-than-expected storm activity in 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, 37 tropical cyclones have formed, with 26 strengthening into named storms. Thirteen of them have intensified into typhoons, and one has become a super typhoon. The ACE index for the season so far is 178.2 units.[7]
Early season activity
Three systems active on July24: Severe Tropical Storm Co-May (far left); Tropical Storm Francisco (upper right); and Tropical Storm Krosa (lower right).
The season officially began with the formation of a tropical depression on February 11 near the Philippines. Four months later, Tropical Storm Wutip developed on June 11, becoming the third-latest named storm on record in the western Pacific basin. It also ended a 169-day period with no named storm activity in the basin. Wutip caused widespread damage across parts of the Philippines, Vietnam, and China, leaving 17 people dead and resulting in US$253million in damage. On the same day, another low-pressure area formed east of the Philippines; it developed into 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 developed off the coast of Japan.
July was notably active, producing eight named storms, including one not recognized by the JMA. The month began with Tropical Storm Mun, which largely spared affected areas. The season's first typhoon, Danas, formed on July 3 and made landfall in Taiwan as a Category1-equivalent typhoon, becoming the first typhoon to strike the island's west-central coast since Typhoon Wayne in 1986. On July 11, two systems formed: Tropical Storm Nari and Tropical Depression 07W. Later in the month, Tropical Storm Wipha developed near the Philippine coast, causing fatalities and significant damage between northern Vietnam and southern China.
By the end of July, three more cyclones had developed: Francisco, Co-May, and Krosa. Co-May affected the Philippine provinces of Pangasinan and Ilocos Sur, the Ryukyu Islands, and eastern China, killing 55 people and causing US$73million in damage. The month concluded with the formation of Tropical Storm Bailu on July 31.
Peak season activity
Two simultaneous active tropical cyclones on September20: 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 Category1 typhoon on September 8, resulting in 12 fatalities. During the peak of the season, three tropical cyclones formed: Mitag, Ragasa, and Neoguri. Typhoon Ragasa became the first super typhoon of the season, eventually reaching Category 5-equivalent status. It impacted the Philippines, Taiwan, Southern China and Vietnam before eventually dissipating.[9] Typhoon Neoguri strengthened into a Category4-equivalent typhoon amid high SSTs, then weakened for a time due to a combination of upwelling and high wind shear, but restrengthened into an unusually high-latitude Category4 typhoon near 40°N, making it one of the strongest unusually high-latitude cyclones on record. Typhoon Bualoi formed on September 22 near the Philippines to the southeast, and caused extensive damages and losses of life in the Philippines and Vietnam.
Late season activity
October began with the formations of Matmo, Halong, Nakri, and Fengshen, one of which became a very strong typhoon. Typhoon Matmo caused extensive flooding in the Philippines and Thailand, resulting in at least 39 deaths and damage amounting to $2.24 billion (2025 USD). On the last day of October, Typhoon Kalmaegi formed, persisting into November and making landfall in the Philippines and later Vietnam, causing extensive damage and loss of life.[10] On the 6th of November, Tropical Storm Fung-wong formed. It rapidly intensified in the Philippine Sea as a Typhoon, and further intensified as a Super Typhoon based on PAGASA.
A tropical depression formed over the South China Sea on June9.[11] On the next day, the JTWC designated it as Tropical Depression 01W.[12] The JMA upgraded it to Tropical Storm Wutip on June11. The storm strengthened further while moving to the west-northwest.[13] At 18:00 UTC, the JMA further upgraded the system to a severe tropical storm.[14] Wutip hit the southwest coast of China's Hainan Island at around 15:00 UTC on June 13,[15] before reemerging over the Gulf of Tonkin shortly after.[16] On June 14, the JTWC reported that Wutip had rapidly intensified into a minimal typhoon, although its deep convection had largely collapsed.[17] Later that day, Wutip made its second landfall near Leizhou City in Guangdong Province at around 12:30 CST (04:30 UTC).[18] After landfall, it weakened into a minimal tropical storm, as satellite imagery indicated that its eye had filled in.[19] 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.[20][21]
On June 11, the JMA announced that a tropical depression had developed east of the Philippines.[22] 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).[23] By the following day, it had intensified into a tropical depression and was named Auring by PAGASA.[24] PAGASA reported that Auring made landfall in Taiwan and later weakened into a remnant low due to the frictional effects of its landfall.[25][26] The agency issued its final advisory when the system exited the PAR,[27] while the JMA continued to monitor it until it was last noted on June 13.[28] 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.[29] Heavy rainfall was recorded in Daliao District, with 205.5mm (8.1in) of precipitation recorded.[30] At least one fatality and four injuries were reported due to the system.[31] 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.[32] In the Philippines, Auring brought moderate to heavy rainfall and thunderstorms to the provinces of Batanes and Cagayan.[25]
A tropical depression formed north of the Northern Mariana Islands on June 21.[33] As it continued to develop, the JTWC designated it 02W on the next day.[34] 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.[35] Steered northwest by a subtropical ridge located to its northeast, Sepat strengthened as its structure improved.[36]
Sepat's convective activity decreased significantly on June 24, halting any intensification.[37] Later that day, the JTWC assessed that Sepat had weakened into a tropical depression as it slowed and entered a drier, more hostile environment.[38] A trough approaching from the west began to impart strong wind shear on the depression as it neared Japan and turned north-northeastward.[39][40] 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.[41]
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.[42] Steered by a subtropical ridge located to its northeast, 03W tracked northwestward and remained poorly organized.[43] The depression made landfall on the eastern coast of the Leizhou Peninsula by 02:00 UTC on June 26,[44] moving inland before dissipating that day.[45]
Heavy rains battered Northeastern Vietnam, triggering a landslide in Yên Bái Province which destroyed a house, killing one person inside.[46] 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.[45]
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.[47] Though its circulation was initially exposed, by July 2 the cyclone had intensified into a tropical storm,[48] and it received the name Mun later that day.[49] Early on July 3, Mun's convection waned as dry air disrupted the cyclone,[50] though it began to recover later that day as deep convection returned.[51][52] 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.[53] 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, a tropical depression formed in the South China Sea, designated 05W by the JTWC and Bising by PAGASA.[54][55] The JMA upgraded it to Tropical Storm Danas, and the storm continued to intensify as it moved to th enorth.[56] At 15:40 UTC on July 6, Danas made landfall at peak intensity near Budai, Chiayi County, Taiwan, making it the first typhoon to make landfall on the western coast of the island since Typhoon Wayne in 1986.[57] After traversing Taiwan, it weakened further.[58] The storm made two more landfalls in Dongtou District, Wenzhou and Rui'an on July 8.[59] 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.[60] Two people died from the effects of the storm in Taiwan, while 726 others were injured.[61] One person also died in the Philippines due to flooding caused by the storm.[62]
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.[63] 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.[64] 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 Chanthu in 2016 and the first on record in July since 1951.[65][66] 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.[67]
Initially peaked as a severe tropical storm, in JMA’s post analysis on October 29, it was reassessed that Nari only reached its peak intensity as a tropical storm.[68]
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.[70][71] 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.[72] By 08:00 PHT (00:00 UTC) on July 16, it developed into a tropical depression and was named Crising by the PAGASA.[73] The JTWC classified it as a monsoon depression due to its large circulation, later issuing a TCFA as convection increased.[74] 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.[75] 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.[76] It gradually intensified into a typhoon before making landfall over Taishan in Guangdong Province.[77] 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.[78][79] 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[80] and affecting over 9.5million people.[81] 40 fatalities, 33 injuries, and eight people missing were reported.[82] In Hong Kong, the HKO raised Hurricane Signal No.10, its highest warning level.[83] At least 33 people were injured, 711 trees were reported downed, and 277 people were evacuated.[84] Losses totaled to US$1.15 billion according to AON.[85]
On 00:00 UTC of July 22, the JMA began tracking on a tropical depression that had formed northeast of Ilocos Norte.[86] It quickly organized over the West Philippine Sea, prompting a TCFA from the JTWC. Soon after, the JTWC and the PAGASA classified it as a tropical depression, with PAGASA naming it Emong and the JTWC designating it 11W. It later intensified into a tropical storm,[87] named Co-May by the JMA. Due to an imminent Fujiwhara effect with Francisco, Co-May looped northeast towards the Ilocos Region.[88] On July 24, all 3 agencies upgraded the storm to a minimal typhoon.[89]
On July 21, the JTWC first noted a low-pressure area south-southwest of Kadena Air Base. The JMA classified the system as a tropical depression on 06:00 UTC of July 22. The JTWC and PAGASA later did the same, with PAGASA assigning the local name Dante and the JTWC designating it as Tropical Depression 10W after initially issuing a TCFA.[101][102] On July 23, the JMA, the JTWC, and PAGASA upgraded the system to a tropical storm, naming it Francisco, as it tracked north-northwestward.[103]
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.[104] 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.[105]
Heavy rain and tropical-storm-force winds were reported in the Ryukyu Islands.[106]
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.[107] Krosa maintained its strength due to marginally favorable environmental conditions despite its fully exposed, ragged LLCC.[108] 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.[109] 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.[110] 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.
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[111] and designated it as 16W.[112] The system was upgraded to a tropical storm and named Podul by the JMA on August 8.[113] Despite initial disruption from northeasterly vertical wind shear, Podul gradually organized,[114] 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.[115] The JTWC followed suit, upgrading Podul to a typhoon later that day, citing improved convective structure despite dry air intrusion.[116] On August 13, Podul made landfall in Taimali, Taitung County in Taiwan at 13:00 TST (05:00 UTC) as a Category2-equivalent typhoon.[117] 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.[118]
In Taiwan, Podul left one person missing, 112 injured, and displaced 8,024 residents.[119] A man in Kaohsiung was killed after falling while repairing a storm-damaged roof.[120] 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.[121]
The JMA 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,[135] 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) south-southwest of Kadena Air Base, noting marginal potential for tropical cyclogenesis.[136] The JMA classified the system as a tropical depression the next day,[137] followed by the PAGASA at 02:00 PHT (18:00 UTC) on August 18, assigning the local name Huaning.[138] Later that day, the JTWC issued a TCFA, citing a consolidating LLCC within a reverse-oriented monsoon trough.[139] Despite initial hindrance from wind shear and dry air,[140] Huaning gradually organized and was designated as 18W by the JTWC at 06:00 UTC. It was upgraded to a tropical storm on August 20[141] 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.[142] Lingling made landfall near Hioki, Kagoshima at 17:00 JST (08:00 UTC) before weakening into a tropical depression,[143] 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.[144]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.[145] It was upgraded by the PAGASA to Tropical Depression Isang on August 22 near Aurora,[146] with the JMA and the JTWC issuing similar classifications.[147] Isang made landfall over Casiguran, Aurora that morning,[148] and was later designated as 19W by the JTWC as it entered the West Philippine Sea.[149] By August 23, the system started to intensify in the South China Sea under favorable conditions,[150][151] becoming a tropical storm and named Kajiki at 01:05 UTC.[152] Despite moderate wind shear, Kajiki reached severe tropical storm strength by 12:50 UTC[152] and was later upgraded to a typhoon by the JTWC.[153] As Kajiki neared Sanya, it strengthened into a Category2-equivalent typhoon with a 23-nautical-mile-wide (43km) eye.[154][155] It then weakened slightly over the Gulf of Tonkin due to lower ocean heat content,[156] undergoing an eyewall replacement cycle while maintaining strong outflow.[157][158] 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[159] and caused extensive flooding in Metro Manila.[160] In Vietnam, Kajiki caused at least four deaths and injured 47 people.[161] 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.[162][163] Flooding also struck Mae Chaem and Mae Hong Son, while in Myanmar, Kajiki's remnants caused flash floods in Tatkon Township, prompting evacuations,[164] and a landslide in Pinlaung Township, Shan State.[165] Losses totaled to US$300 million according to AON.[85]
On August 23, the PAGASA began monitoring a low pressure area east of Surigao del Sur, noting a high chance of development.[166][167] The JMA briefly classified the system as a tropical depression on August 27 but downgraded it before reinstating the classification.[8] PAGASA upgraded it to a tropical depression on August 28 and named it Jacinto, replacing Jolina. The JTWC later issued a TCFA and designated the system as 20W.[168] Moving westward into the South China Sea, the system encountered marginal conditions, including upper-level northerly flow and exposed low-level circulation.[169] On August 30, it strengthened into a tropical storm and was named Nongfa by the JMA, exhibiting improved convection and banding.[170] Nongfa made landfall between Quảng Trị and Hà Tĩnh provinces in Vietnam on August 30,[171] weakening as it crossed mountainous areas in Vietnam and Laos. Both the JMA and JTWC issued final advisories on August 31 as the system dissipated. Its remnants later crossed into the Bay of Bengaland eventually redeveloped into Deep Depression LAND 04 over the Arabian Sea on September 6.[citation needed]
In Central Vietnam, Nongfa brought heavy rains and flooding that cut off roads and isolated mountain villages in Quảng Trị and Hà Tĩnh.[172] Over 165 residents were evacuated in Quảng Trị, and landslides, road subsidence, and infrastructure damage were reported. Meanwhile, in Thailand, Nongfa's remnants and the ongoing monsoon trough caused widespread flooding in the Pa Sak, Yom, and Nan basins.[173] Districts in Phetchabun Province and Phitsanulok reported flash floods and crop damage. Authorities activated emergency response centers, controlled dam releases, and coordinated evacuations to mitigate further impacts.
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.[184] 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.[185] 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.[186][187] Flooding was reported in Kamakura.[188] 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.[189]
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.[190] 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).[191] At 02:00 PHT on September 6 (18:00 UTC), PAGASA upgraded the disturbance to a tropical depression, assigning it the local name Lannie.[192] The JTWC issued a TCFA later that same day, citing a high chance of further development.[193] Around 09:00 UTC, the JTWC subsequently upgraded the system to a tropical depression, designating it as 22W.[194]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.[195] Satellite imagery showed that Tapah had a partially exposed LLCC, with deep convection organizing over the center as it tracked northwestward on September 7.[196] 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.[197] 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.[197] Both agencies made their last warning afterwards as the typhoon interacted with the rugged terrain over Southern China, causing it to rapidly dissipate.[197]
Tapah caused 12 injuries in Hong Kong and generated minor flooding in Macau.[198]
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.[199] The next day, the JMA classified the system as a tropical depression at 15:00 JST (06:00 UTC),[200][201] and PAGASA named it Mirasol at 14:00 PHT.[202] The JTWC issued a Tropical Cyclone Formation Alert at 03:30 UTC,[203] and later upgraded the system to 23W at 09:00 UTC.[204] The HKO also reported its development.[205][206] Mirasol made landfall over Casiguran, Aurora at 03:20 PHT on September 17.[207] It weakened over the Cordillera Central before re-emerging into the West Philippine Sea.[208][209] At 15:00 JST on September 18, the JMA upgraded the system to Tropical Storm Mitag.[210] Mitag intensified over the South China Sea but later encountered dry air and land interaction, prompting the JTWC to issue its final advisory.[211][212] Mitag made landfall near Shanwei, Guangdong and was later downgraded to a tropical depression by the JMA.[213] The JMA later made its final warning at 21:00 JST (12:00 UTC) of September 20 as it dissipated.
Mitag caused flooding in the Philippines, killing three people and leaving four missing in Valencia, Bukidnon.[214]
On September 16, the JTWC identified a tropical disturbance north of Yap.[215] It developed into a tropical depression the next day, according to the JMA,[216] and was named Nando by PAGASA upon entering the Philippine Area of Responsibility (PAR).[217] The system intensified over the Philippine Sea, becoming Tropical Storm Ragasa on September 19,[210][218] and reached typhoon strength the next day.[219] On September 21, both PAGASA and the JTWC upgraded Ragasa to a super typhoon, with the JTWC estimating 1-minute winds of 270 km/h and pressure of 910hPa (26.87inHg).[220][221] The JMA assessed ten-minute winds of 205 km/h and pressure of 905hPa (26.72inHg).[222] Ragasa made landfall over Panuitan Island in Calayan, Cagayan on September 22.[223] After brushing the Babuyan Islands, the typhoon began to weaken gradually, underwent an eyewall replacement cycle that produced a 25-nautical-mile-wide (46km; 29mi) eye as it tracked west-northwestward toward the South China Sea.[224] It made landfall at Hailing Island in Yangjiang, Guangdong on September 24,[225] and in Beihai, Guangxi as a tropical storm the next day.[226] It later struck Quảng Ninh province in Vietnam as a tropical depression,[227] and dissipated soon after.[citation needed]
The Hong Kong Observatory issued Hurricane Signal No. 10 on September 24 for the second time this year since Wipha two months before, which has been the first time in over 60 years that the Hurricane Signal No. 10 has been issued twice in a year.[228] A total of at least 11 deaths and 11 injuries were caused by Ragasa in the Philippines,[229] 18 deaths and 107 injuries in Taiwan due to flooding,[230] and injured 101 people in Hong Kong.[226]
On September 17, the JTWC identified an area of convection about 219 nautical miles (406km) north of Wake Island, showing a weak low-level circulation with flaring convection.[231] The JMA classified the system as a tropical depression later that day and named it Neoguri after upgrading it to a tropical storm at 22:20 JST (13:20 UTC).[232][210] By September 19, Neoguri strengthened into a severe tropical storm under favorable conditions with 29–30°C (84–86°F) sea surface temperatures.[233] Both the JMA and JTWC upgraded it to a typhoon on September 20 as a ragged eye formed and rapid intensification began.[234][235] Neoguri reached "very strong" typhoon status at 18:00 JST (09:00 UTC) on September 20 and intensified rapidly, gaining 55 knots (102km/h; 63mph) in 24 hours.[236][237] On September 21, the JMA classified Neoguri as a violent typhoon with a central pressure of 920hPa (27.17inHg).[238] It peaked as a Category 4-equivalent typhoon with winds of 230 km/h (145 mph) before gradually weakening as wind shear and interaction with a mid-latitude trough increased.[239][240] The JTWC downgraded Neoguri to a tropical storm on September 24, briefly reclassifying it as a typhoon later that day.[241][242]
On September 27, Neoguri rapidly re-intensified into a Category 4 typhoon near 40°N, becoming one of the strongest high-latitude cyclones on record before completing its extratropical transition on September 28.[243][242]
On September 22, JTWC began monitoring an area of convection northeast of Yap in a marginally favorable environment.[244] The next day, the JMA classified it as a tropical depression,[245] and the JTWC issued a TCFA.[246] At 16:00 PHT (08:00 UTC), the system entered the Philippine Area of Responsibility as Opong.[247] By early September 24, the JTWC designated it as Tropical Depression 26W, and the JMA named it Bualoi.[248] It was later upgraded to a tropical storm by JTWC, and then a severe tropical storm by PAGASA and JMA.[249][250] On September 25 at 11:30 PHT (03:30 UTC), Bualoi made landfall as a typhoon over San Policarpo, Eastern Samar,[251][252] then weakened before making five more landfalls in Palanas and Milagros, Masbate; San Fernando and Alcantara, Romblon; and Mansalay, Oriental Mindoro on September 26, 2025.[253] After emerging into the Mindoro Strait, Bualoi reintensified into a minimal typhoon and showed signs of rapid deepening.[254][255] Entering the South China Sea, the system intensified further under low wind shear and abundant moisture.[256] Satellite and radar data showed an asymmetric structure and a ragged eye with defined rainbands reaching Vietnam.[257] Bualoi reached its peak intensity as a Category2-equivalent typhoon before making landfall in Hà Tĩnh, Vietnam on September 29.[258] The JTWC issued its final advisory as the storm moved inland over Laos.[259]
Bualoi caused damage in parts of the Philippines and left 37 people dead and another 13 missing.[260][261] More than 400,000 people were displaced. In Vietnam, at least 51 people died, 153 were injured and 14 others went missing,[262][263] while around 300,000 people were evacuated.[264]
On September 29, the JTWC identified a low-pressure area about 241 nautical miles (446km) north-northeast of Yap, with satellite imagery showing disorganized convection along its western side.[265] Entering the PAR on October 1, it was named Paolo by PAGASA, while the JMA classified it as a tropical depression.[266][267] The JTWC issued a TCFA and later dubbed the system as 27W, citing increased convection and fragmented banding.[268][269] Upgraded to a tropical storm the next day, it was named Matmo by the JMA.[270] By 23:00 PHT (15:00 UTC), PAGASA classified Matmo as a severe tropical storm amid improved convective organization.[271][272] On October 3, Matmo made landfall in Dinapigue, Isabela as a typhoon,[273] then weakened while crossing Luzon before emerging over the West Philippine Sea.[274] The JTWC reupgraded it to a typhoon on October 4 due to improved banding and cooling cloud tops.[275] On October 5, Matmo peaked as a Category 2-equivalent typhoon with 1-minute sustained winds of 165 km/h (105 mph) and a central pressure of 968 hPa.[276] Matmo later made landfall over Xuwen County in Guangdong at around 14:50 CST.[277] It made another landfall over Fangchenggang,[278]Guangxi Province early on October 6 at 01:10 CST[279][280] after it entered the Gulf of Tonkin.[281] Afterwards, it moved over Vietnam, rapidly deteriorating until its dissipation on October 7.[276]
Heavy rainfall from Matmo on October 3 caused flooding across parts of Luzon and left one person dead.[282] In Aurora, over 21,000 people were evacuated.[283] Flash floods in Batangas prompted the evacuation of hundreds of families, while 55 families in Ifugao were relocated following the opening of Magat Dam's gates.[284] At least eight people were killed by the storm in Vietnam,[285] along with 22 people in Thailand.[286]
On October 3, a broad area of convection developed about 264 nautical miles (489km) southeast of Iwo Jima, lacking a defined low-level circulation. The system was in a marginally favorable environment with 15–20 knots (28–37km/h; 17–23mph) wind shear, 28–29°C (82–84°F) sea surface temperatures, and moderate outflow aloft.[287] The JMA classified it as a tropical depression on October 4.[288] The system's center became obscured by persistent convection,[289] and JTWC issued a TCFA later that day.[289] JTWC upgraded it to Tropical Depression 28W nine hours later.[290] 28W became Tropical Storm Halong early on October 5.[291] It later strengthened into a severe tropical storm and then a typhoon, with JTWC noting a developing eye and organized outflow.[292] JMA also upgraded Halong to typhoon status on October 7.[293] That day, it rapidly intensified to Category 4 strength, developing a clear eye.[294] Halong tracked northeastward on October 8, maintaining intensity despite a less symmetrical eye.[295] It began weakening the next day due to 25–30 knots (46–56km/h; 29–35mph) wind shear and dry air.[296] JTWC issued its final advisory on October 10 as Halong transitioned into an extratropical system.[297] JMA continued monitoring it until declaring it extratropical at 22:10 JST (13:10 UTC).[298]
Halong generated strong waves that left one person dead in Japan.[299] In Hachijojima, wind speeds were measured at 107 knots (123mph) and record rainfall amounts of 349 millimetres (13.7in) were observed.[300] Over 2,700 customers lost water on the island and another 2,200 customers lost power. Several roads were left impassible on these islands due to flooding and downed trees.[301] In Western Alaska, flood and high wind watches were issued as the extratropical remnants of Halong approached, bringing hurricane-force winds to the Bering Sea.[302] The storm caused widespread damage in the Yukon-Kuskokwim Delta, where winds reached 107 miles per hour (172km/h) in the Kusilvak Mountains.[303] Record flooding hit Kipnuk and Kwigillingok, where homes were swept away and several residents went missing.[304] One fatality was confirmed in Kwigillingok, with two others missing.[305]
On October 6, the JTWC identified a disorganized area of low-pressure that had formed 205 nautical miles (380 km) southeast of Guam, with satellite imagery depicting an area of persistent convection embedded within the southern periphery. Environmental analysis confirmed that the disturbance was in a marginal environment, characterized by moderate wind shear (15–20 kts), moderate southerly outflow, and warm sea surface temperatures (29–30°C).[306] Later that day, the JMA classified the disturbance as a tropical depression, located at 13°N147°E / 13°N 147°E / 13; 147.[307] The JTWC later issued a TCFA at 03:00 UTC, citing a high chance of development.[308] Both the JMA and the JTWC upgraded their classification into a tropical storm late on October 8, naming it Nakri and 29W respectively, as it continued to gradually intensify over favorable environment.[309][310][311] At 12:40 PHT (04:40 UTC) on October 9, the system entered the PAR and was named Quedan by PAGASA.[312] Despite being in warm waters, vertical wind shear and dry air environment hindered Nakri from intensifying further at that time as it stalled near the Ryukyu Islands.[313] At around 03:00 JST (18:00 UTC) of October 12, JMA upgraded Nakri into a severe tropical storm as it slowly moved north-northeastwards.[314] Nakri then moved east-northeast towards south of Camp Fuji, Shizuoka prefecture, gradually intensifying into a Category 1-typhoon according to the JTWC later that evening, with the JMA following suit early on October 13.[315][316] Gradual weakening ensued later that day as the typhoon encountered unfavorable conditions.[317] As it moved through the baroclinic zone on October 15, the JTWC ceased issuing advisories on Nakri as it began extratropical transition.[318]
As Nakri passed close to the island of Hachijō-jima, a sustained wind speed of 153.7 kilometres per hour (95.5mph) was measured, while rainfall totaled over 130 millimetres (5.1in) within a 12-hour period.[319]
On October 12, the JMA began tracking a tropical depression that had formed around 5°N148°E / 5°N 148°E / 5; 148.[316] Later that day, the JTWC also began monitoring the system, noting poorly organized convection along its southern periphery within a moderately favorable environment of warm sea surface temperatures and low wind shear.[320] By October 15, the JMA downgraded it to a low-pressure area, though the JTWC continued tracking the disturbance south of Guam, where satellite imagery showed a weak, wave-like structure.[321] It entered the Philippine Area of Responsibility at 15:00 PHT (07:00 UTC),[322] and was named Ramil by PAGASA early the next day.[323] A Tropical Cyclone Formation Alert was issued by the JTWC at 03:00 UTC, and at 02:00 PHT (18:00 UTC) on October 18, PAGASA upgraded Ramil to a tropical storm.[324][325] The JMA soon named it Fengshen and the JTWC designated it as 30W.[326][327] Fengshen made its first landfall over Gubat, Sorsogon on October 18 and then crossed the Bicol Region, making further landfalls over Alabat and Mauban, Quezon on October 19.[328][329] It later passed through Manila Bay and made a final landfall at Samal, Bataan before emerging over the South China Sea.[330] The storm briefly weakened into a tropical depression before restrengthening the next day.[331][332] Moving westward under a subtropical ridge, Fengshen peaked as a severe tropical storm before weakening again due to dry air and southwesterly wind shear.[333][334] It eventually dissipated off the coast of Vietnam on October 23.[335]
Fengshen generated strong winds, landslides and flooding across the Philippines that killed seven people and left two others missing.[336] Five people were killed by a tree that fell on a house in Pitogo, Quezon,[337] while one person was killed while three others were injured in flash floods in Roxas City,[338] which was subsequently placed under a state of calamity.[339] One person was injured after being pinned down in a collapsed house in Estancia, Iloilo, while two people went missing after a vehicle was hit by a landslide in Bukidnon.[340]
The JMA began tracking a weak tropical depression at 18:00 UTC on October 20.[citation needed] On October 21, the JTWC also started to monitor the same system as a tropical disturbance that was situated about 20 nm (37 km) southeast of Ishigakijima. Satellite imagery indicated an area of flaring convection with no defined LLCC, embedded within marginal conditions.[341] At 00:00 UTC of the following day, PAGASA named the depression Salome.[342] Early on October 23, PAGASA upgraded Salome into a tropical storm despite being unrecognized by other agencies in that intensity.[343] However, PAGASA eventually downgraded Salome back into a tropical depression[344] and reclassified it into a low pressure area later that day, with JMA also ceasing advisories on Salome.[345]
On October 22, Signal No. 2 was issued in Batanes. Meanwhile, a Signal No. 1 warning was issued in western portions of Babuyan Islands, and northwestern portions of Ilocos Norte.[346]
A tropical disturbance formed on October 30 about 313 nautical miles (580 km) east-southeast of Yap, with satellite imagery showing cycling convection over a weak low-level circulation center.[347] The JTWC designated it as 31W, and the JMA upgraded it to Tropical Storm Kalmaegi at 22:30 JST (13:30 UTC) on November 1.[348][349] Entering the Philippine Area of Responsibility at 05:30 PHT (21:30 UTC) on November 2, it was named Tino by PAGASA.[350] Kalmaegi strengthened into a severe tropical storm later that day,[351] and a Category 1 typhoon on November 3.[352][353] Reaching Category 2 intensity, Kalmaegi made landfall over Silago, Southern Leyte around 00:00 PHT (16:00 UTC) on November 4,[354] followed by multiple landfalls in the Visayas and Palawan, including Borbon, Cebu, Sagay, Negros Occidental, San Lorenzo, Guimaras,[355]Iloilo City,[356]Magsaysay, Batas Island in Taytay,[357] and El Nido, Palawan.[358] After crossing the Philippines, Kalmaegi entered the South China Sea on November 5, intensifying into a Category 3 typhoon early the next day before weakening under increasing wind shear. It made landfall over Gia Lai and Đắk Lắk, Vietnam, on November 6,[359][360] and quickly dissipated inland. The JTWC issued its final advisory on November 7.[361]
Kalmaegi brought strong winds and floods that left at least 224 people dead, 526 injured, and 109 missing in the Philippines, mostly in Cebu.[362] A Philippine Air Force helicopter crashed while on a disaster reconnaissance mission in Loreto, Agusan del Sur, killing six people.[363] The scale of the disaster led President Bongbong Marcos to declare a nationwide state of calamity on November 6.[364] In Vietnam, the storm left at least five dead, six injured, and three missing.[365] Kalmaegi also caused flooding that killed 13 people in Thailand.[366]
On November 3, the JTWC began tracking an area of convection that developed approximately 300 nm (556 km) northeast of Chuuk, with satellite imagery depicting a poorly defined LLCC with localized bursts of convection within the southern periphery. However, the disturbance is in a favorable environment, characterized by low vertical wind shear (5–19 kts), moderate poleward upper-level outflow, and 29–30°C (84–86°F) warm sea surface temperatures.[367] JMA later followed suit later that day, marking the disturbance as a depression. On the following day, the depression later became Tropical Depression 32W by the JTWC as the disturbance continued to become better organized.[368] As 32W maintained its strength at that time, it shifted eastwards due to the steering influence of the subtropical ridge to the north. Satellite imagery showed an exposed LLCC around the broad and expansive system.[369] 32W later became better organized early on November 6, resulting in the formation of Tropical Storm Fung-wong as it started to move west-northwestwards.[370] Later that day, Fung-wong was upgraded into a severe tropical storm as it moved westwards through very warm sea surface temperatures.[371] Despite still being outside the Philippine Area of Responsibility, Fung-wong was assigned the local name Uwan by PAGASA at 17:00 PHT (09:00 UTC) of the next day, marking only the second time the agency has done so since Pabuk in 2024, due to the need to hoist wind signals because of the extremely large size of the storm.[372] Satellite imagery also indicated that a large eye feature had formed, with a deep convection tightly wrapping on all sides.[373] Early on November 8, Fung-wong strengthened into a typhoon.[374] Later that day, high wind shear (25-30 kts) caused the typhoon to slightly slow down its intensification as it moved towards Luzon;[375] however, intensification would gradually resume during the early hours of November 9, with the JTWC upgrading Fung-wong to a Category3-equivalent typhoon and the JMA upgrading it to a "very strong" typhoon in accordance with the latter's tropical cyclone intensity scale.[376][377] Satellite imagery also depicted that the eye of the typhoon became cloud-filled and slightly asymmetric as it battled easterly wind shear.[378] At 08:00 PHT (00:00 UTC) on November 9, PAGASA reported that Fung-wong rapidly intensified into a super typhoon, with estimated winds of 185 km/h (115 mph) despite other agencies maintaining the intensity.[379] PAGASA also estimated that Fung-wong had reached a diameter of 1,800km (1,100mi).[380] At 09:00 UTC, JTWC further intensified and reached its peak intensity of a Category 4-typhoon, with estimated 1-minute winds of 215 km/h (130 mph) and a pressure of 943 hPa (27.85 inHg).[381] Around 21:10 PHT (13:10 UTC), Fung-wong made landfall over Dinalungan, Aurora.[382] Afterwards, the system weakened significantly as it moved over the vicinity of Bagulin, La Union[383] before it reemerged over the coastal waters of that province, with a weakened convective structure as it became disorganized.[384] As it moves through the West Philippine Sea, Fung-wong starts to curve northwestwards along the southern periphery of the subtropical ridge as the weakening trend continues.[385]
Fung-wong left eight people dead and four others injured in the Philippines.[386]
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.[387][388] 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).[389] As a result, the JTWC stopped tracking the system the next day, noting that it had dissipated.[390] The JMA kept tracking the depression until it dissipated on February 15.[391] Although it regenerated the next day,[392] the JMA stopped tracking it by February 17.[393] 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.[394] Some towns, like Nhà Bè, saw their highest rainfall in 41 years.[395] 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.[396] 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.[388]
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.
A tropical depression formed north of Wake Island on August 2.[399] Two days later, the JTWC designated it as Tropical Depression 14W, although the circulation was fully exposed.[400] The system dissipated late on August 4 and merged with another disturbance just southwest of Wake Island.[401]
A tropical depression formed northwest of Wake Island late on August 4, to the south of the remnants of 14W.[401] Early on August 6, the JTWC designated the depression 15W. Dry air and strong wind shear prevented strengthening, and the depression dissipated later that day.[402][403]
On August 8, a tropical depression developed near northern Luzon. At 08:00 PHT (00:00 UTC), PAGASA likewise upgraded the system to a tropical depression and named it Fabian.[404] Wind shear prevented further development, and the depression dissipated on August9.[405]
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.[406] 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).[407] PAGASA names tropical cyclones which move into or form as a tropical depression in their PAR, located between 135°E-115°E and between 5°N-25°N, even if the cyclone has had an international name assigned to it.[406] The names of significant tropical cyclones are retired, by both PAGASA and the Typhoon Committee.[407] 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 2026.[407]
A tropical cyclone is named when it is judged to have 10-minute sustained wind speeds of 65km/h (40mph).[408] 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.[409] 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 after the 2019 season. The names Co-May, Nongfa, and Ragasa were used for the first time this season.
PAGASA uses its own naming scheme for storms that develop in or enter their self-defined area of responsibility.[410] During this season, PAGASA is using the following list of names, which was last used during 2021 and will be used again in 2029, updated with replacements of retired names, if any.[410] 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.[410] All three new names were used for the first time this season, as well as Uwan after replacing Urduja in 2017, but it was unused in 2021.
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.
↑ The Joint Typhoon Warning Center is a joint United States Navy–United States Air Force task force that issues tropical cyclone warnings for the western Pacific Ocean and other regions.[2]
↑ Plus 01C; 07W is a subtropical depression according to the Joint Typhoon Warning Center (JTWC).
↑ 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 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.
