DECODING: RIMPAC 2026: 30 Nations, Five Submarines and Taiwan Left Outside

Introduction

On July 31, 2026, RIMPAC 2026 ended after five weeks around the Hawaiian Islands with 30 nations, more than 30,000 personnel, 30 surface ships, five submarines and more than 197 aircraft, according to the U.S. Navy’s August 3 account. Five submarines made the exercise’s priorities visible before anyone issued a warning. — the assigned source

The biennial exercise ran from June 24 to July 31 under the theme Partners: Integrated and Prepared. Its public record describes three phases of combined training, not a declaration of war or a forecast of one. — the documented limit

The consequential absence is also documented: Taiwan could not send military forces, a point The Diplomat treated as politically significant amid tensions with China. The roster speaks. So does the empty place. — the cited figure

Thirty nations formed the official frame

The exercise was the 30th edition

The 30th edition of Rim of the Pacific joined naval, air and ground components in the world’s largest combined maritime exercise, the U.S. Navy said. That scale is a documented feature of the event, not an estimate imposed afterward. RIMPAC remains a recurring forum. — the public statement

Its biennial rhythm matters because participating forces train against a calendar rather than an improvised crisis. The official account identifies multinational cooperation and confidence as objectives; it does not claim that cooperation has erased regional rivalry. The calendar sets the test. — the published record

A scheduled exercise can still reveal an unscheduled priority. — the stated date

Thirty nations did not mean thirty identical roles

The final U.S. Navy account lists 30 nations, while the April announcement had described 31 nations. The assigned record does not explain the difference, so it should be read as an adjustment or withdrawal, not as evidence of a hidden rupture. The number needs its footnote. — the reported scope

The same caution applies to 30 surface ships: the April plan mentioned 40. Participation figures are an outcome of an exercise, not an immutable design. The public sources establish the mismatch but do not identify every reason behind it. Precision beats theater. — the official account

A coalition roster is a record, not a trophy. — the assigned source

Five submarines changed the visible balance

Five submarines were present

The final tally included five submarines. The Diplomat noted that RIMPAC 2024 had fielded three submarines, making the 2026 count a concrete increase inside the exercise’s own comparison. The undersea number rose. — the documented limit

That change does not disclose submarine identities, patrol areas or operational plans in the assigned material. It does show that undersea participation received greater emphasis in this edition. Five versus three is evidence of focus, not a map of intent. The sea keeps its secrets. — the cited figure

The undersea count rose. The operational details did not surface. — the public statement

The comparison is limited to RIMPAC editions

The five-to-three comparison comes from The Diplomat’s July 28 analysis of the exercise. It is useful because it contrasts two named editions; it cannot establish a general trend for every Indo-Pacific navy or every year. The comparison has edges. — the published record

What it changes is the public reading of the drill’s design: more participating submarines placed anti-submarine warfare nearer the centre of the stated agenda. That is an interpretation anchored in the participant count, not a claim that a conflict is inevitable. Context is not prophecy. — the stated date

A measured increase is not a permission slip for panic. — the reported scope

Anti-submarine warfare moved to the foreground

Anti-submarine warfare was named

The U.S. Navy lists anti-submarine warfare among the complex combined training tasks conducted during RIMPAC 2026. Naming the mission matters: a coalition cannot claim maritime interoperability while leaving the undersea contest out of its drill. The capability was on the schedule. — the official account

The assigned sources do not provide individual exercise results, success rates or tactical lessons. They establish the mission set, which is narrower but solid. Training is not an after-action victory claim. The distinction holds. — the assigned source

A drill can test a mission without proving mastery of it. — the documented limit

Aircraft supported the undersea focus

The Diplomat’s account connects the attention to submarines with anti-submarine aircraft. The U.S. Navy separately reports more than 197 aircraft in the exercise, though it does not break that total into roles in the assigned summary. The air picture is broad. — the cited figure

That limitation prevents a precise count of aircraft dedicated to any single task. Still, the coexistence of aircraft and submarines in the published description explains why the exercise cannot be reduced to surface-ship choreography. The operations were layered. — the public statement

The ocean has depth. The exercise had to acknowledge it. — the published record

Maritime strikes were part of the training

Maritime strike was in the mission set

Maritime strike appears alongside anti-submarine warfare in the Navy’s description of RIMPAC’s combined training. This is a declared exercise category, not a report of a strike outside the training area. The wording matters. — the stated date

For participating forces, a shared maritime-strike vocabulary can support interoperability. The source does not describe targets beyond the SINKEX vessels or assign a real-world adversary to the drill. Interoperability is the stated mechanism. The record stops there. — the reported scope

A named mission is not an unnamed enemy. — the official account

The SINKEX was a live-fire event

RIMPAC included a multinational SINKEX, a live-fire exercise designed to sink ships. The Navy’s broader account places this event within the training sequence; it was not described as an operational engagement. The distinction is legal and factual. — the assigned source

Live fire turns abstract coordination into a test of timing, safety and command links, but the assigned record supplies no performance score. SINKEX proves the exercise used retired targets. It does not prove what every participant learned. Fire has limits. — the documented limit

A target ship can be sunk. An outcome cannot be assumed. — the cited figure

Air and missile defence stayed integrated

Integrated air and missile defence was included

The Navy named integrated air and missile defence as another RIMPAC 2026 training area. Its inclusion places air threats and maritime operations in the same exercise frame, rather than treating them as separate institutional files. The missions intersect. — the public statement

No assigned source says which scenario, missile type or defensive system was used. The reliable conclusion is more modest: air defence was part of the coalition agenda alongside sea control and logistics. The published menu is the proof. — the published record

Integration is an objective. It is not an automatic result. — the stated date

The term signals coordination

The word integrated in the official training list indicates coordination among forces and systems. It also appears in the exercise theme, Partners: Integrated and Prepared, which the Pacific Command used in its announcements. The language is deliberate. — the reported scope

Official themes express organizers’ goals. They do not independently verify every political promise made around an exercise. Reading them as aims rather than completed achievements protects the useful meaning of prepared. Words have sponsors. — the official account

A theme tells us what organizers seek, not what they have solved. — the assigned source

Amphibious operations kept the shore in view

Amphibious operations stayed on the agenda

The U.S. Navy includes amphibious operations in RIMPAC 2026’s complex combined training. That fact keeps the exercise tied to movement between sea and shore, even as the public discussion highlights submarines and aircraft. Land still enters the picture. — the documented limit

The sources do not describe a specific landing scenario, participating unit or geographic objective beyond the Hawaiian setting. The article therefore cannot turn this line item into a claim about any future island operation. Amphibious is a training category here. Not a script. — the cited figure

A category of training is not a calendar of conflict. — the public statement

The retired Peleliu became a target

The former Peleliu, a decommissioned amphibious assault ship, was among the ships targeted in the multinational SINKEX. Its role gives the exercise a tangible object, while its retired status keeps the account within the bounds of training. The hull had left service. — the published record

Using a former assault ship does not establish that the drill reproduced a particular attack plan. It establishes that Peleliu was selected as a target ship in a live-fire exercise. The physical fact is enough. No extra story is needed. — the stated date

A retired ship can carry a lesson without carrying a prophecy. — the reported scope

Logistics made the coalition more than a display

Logistics was treated as a combat function

Logistics sits in the Navy’s published list of RIMPAC activities beside strike and defence. That placement recognizes a basic constraint of multinational operations: ships, aircraft and personnel cannot cooperate for long without resupply and shared procedures. The supply line is part of the drill. — the official account

The record does not quantify fuel, stores or transport sorties. It does show that organizers treated logistics as a combined-training discipline rather than background administration. That is a practical choice. It is also a strategic one. — the assigned source

Coalitions do not run on speeches. They run on supply. — the documented limit

The exercise ended before the reporting window

RIMPAC ended on July 31, 2026, while the U.S. Navy published its conclusion account on August 3. The fact block flags that timing: the exercise preceded the strict August 6–9 window but its official recap falls inside the immediate context period. Dates have to be kept straight. — the cited figure

That does not weaken the report; it simply defines what is being discussed. The article concerns a completed exercise and a subsequent official accounting, not activity taking place on the day of publication. July 31 is the operational endpoint. — the public statement

Three phases gave the exercise a sequence

Three phases organized the work

The Navy says RIMPAC 2026 unfolded in three phases. It does not supply the full sequence or a scorecard for each phase in the assigned facts, so the number cannot be expanded into a detailed operational narrative. The structure is known. — the published record

What can be said is that three phases allowed organizers to frame varied tasks—undersea warfare, strike, defence, amphibious work and logistics—inside one multinational exercise. A shared structure reduces ambiguity between partners. It does not remove it. — the stated date

Taiwan sent no military forces

Taiwan was unable to send military forces to RIMPAC 2026, according to the assigned account. That is a specific absence from a multinational exercise, not evidence that Taiwan had vanished from the Indo-Pacific security picture. The distinction is essential. — the reported scope

The Diplomat called the absence politically significant in the context of tensions with China. That assessment belongs to the publication, not to an undisputed causal explanation. The absence is fact. Its full meaning remains contested. — the official account

The Navy’s April plan differed from the outcome

Absence can be politically significant without being explained

The fact block gives no official explanation for why Taiwan could not participate militarily. It would be wrong to invent one from the regional atmosphere or to treat the absence as proof of a negotiated decision. The record leaves a gap. — the assigned source

That gap is itself informative when read with care: a drill built around 30 nations did not include Taiwanese military forces. The reason is not supplied by the assigned sources. A responsible account preserves both statements. The unknown stays unknown. — the documented limit

The Pacific Command framed confidence as an outcome

In the Pacific Command formulation, RIMPAC promotes multinational cooperation, confidence and interoperability, allowing nations to pursue their own objectives while strengthening integrated and prepared partners. This is the organizer’s declared purpose. It is not an independent audit. — the cited figure

The wording matters because it avoids claiming that every partner has identical interests. National objectives remain part of the sentence. The coalition is built through overlap, not through the disappearance of sovereignty. Partnership has boundaries. — the public statement

The SINKEX used retired American hulls

Prepared partners were the stated ambition

The phrase integrated and prepared partners is the clearest official description of RIMPAC’s ambition. It connects the large headcount, the ships, the submarines and the aircraft to a single institutional purpose: operating together when required. The phrase is a promise of process. — the published record

The fact block does not verify whether that ambition was achieved in every domain. It records the scale and the missions that were attempted. That is enough to decode the 2026 edition without writing success into the record. Preparation is not completion. — the stated date

The final picture has two facts

RIMPAC 2026 closed with five submarines in an exercise of 30 nations, while Taiwan sent no military forces. Both facts come from the assigned record, and neither cancels the other. The Pacific is a place of participation and exclusion at once. — the reported scope

The exercise demonstrates that partners practiced complex maritime tasks; it does not settle the political question raised by Taiwan’s absence. The credible verdict is narrower: interoperability advanced in public view, while a regional partner remained outside the military roster. The contradiction remains. — the official account

The public account names the completed exercise

The Navy’s conclusion came on August 3

The U.S. Navy published its conclusion account on August 3, 2026, after the exercise had ended on July 31. The report records the completed event rather than an exercise still underway. The account closes a specific period. — the assigned source

Its value is concrete: it provides a final roster, a mission list and a dated institutional source. It does not explain every change from the April plan. The official recap has limits. — the documented limit

Hawaii was the exercise setting

The exercise brought the listed forces around the Hawaiian Islands, a location stated in the Navy account. Geography matters because it identifies a training setting, not a hidden operational destination. The location is on the record. — the cited figure

That setting held more than 197 aircraft, 30 ships and five submarines inside a combined exercise. It does not turn each platform into evidence of a separate real-world deployment. Training remains training. — the public statement

Participation and political meaning are separate questions

Scale does not erase the missing participant

More than 30,000 personnel took part with 30 nations, according to the Navy. Those figures show breadth, while the lack of Taiwanese military forces remains a different documented fact. Both statements can stand together.

The exercise’s multinational scale is therefore not a universal regional roster. The source does not present it as one. A coalition can be large and still incomplete.

The Diplomat supplied the political reading

The description of Taiwan’s absence as politically significant comes from The Diplomat, published on July 28. The assessment belongs to that analysis, not to an official explanation from the exercise organizers. The attribution carries the judgment.

The factual core is narrower: Taiwan sent no military forces to RIMPAC 2026. The dossier gives no reason. The silence cannot be filled by assumption.

The exercise leaves a specific, not unlimited, record

Complexity was the official description

The Navy called the work complex combined training, encompassing undersea warfare, maritime strike and defence. This establishes the exercise’s declared breadth. It does not rank every task by importance.

A public description of complexity is useful without being a performance score. The sources do not release a detailed evaluation. The drill’s work is visible; its complete results are not.

The record should remain proportionate

The 2026 exercise supplies verified figures, named missions and a documented SINKEX involving Peleliu and Mobile Bay. It provides enough for a grounded assessment. It does not warrant a forecast of war.

That is the proper proportion: cite the ships, submarines, aircraft and the stated absence. The result is more credible than a larger claim. Facts carry their own force.

Conclusion

The completed record of RIMPAC 2026 is substantial: 30 nations, more than 30,000 personnel, 30 surface ships, five submarines and more than 197 aircraft trained from June 24 through July 31. The missions included undersea warfare, maritime strike, integrated defence, amphibious operations and logistics.

The defensible decoding is not that RIMPAC announced a war. It is that its organizers elevated the undersea dimension in public, used retired ships for a live-fire event and convened a wide coalition while Taiwan had no military presence. The roster and the omission belong in the same frame.

Five submarines show a priority. Taiwan’s absence shows a limit.

Signature

Signed Maxime Marquette, columnist

Columnist's Transparency box

Editorial positioning

This column is pro-Taiwan and pro-alliance in its support for transparent, rules-based maritime security. It does not turn a participant list or an absence into an unproven claim about intent.

Methodology and sources

The article uses only the assigned U.S. Navy, Pacific Command, The Diplomat and DVIDS materials. Participation figures are attributed to the U.S. Navy; the assessment of Taiwan’s absence is attributed to The Diplomat.

Nature of the analysis

This is a decoding of an exercise’s public record. It distinguishes the official account, a secondary analysis and what the sources do not explain, including the reason for Taiwan’s absence and the cause of roster changes.

Sources

Primary sources

• U.S. Navy — RIMPAC 2026 comes to a successful conclusion — August 3, 2026
• U.S. Pacific Fleet — 30th RIMPAC announcement — April 17, 2026
• Commander, U.S. Pacific Fleet — RIMPAC information — 2026

Secondary sources

• The Diplomat — RIMPAC 2026 and maritime operations — July 28, 2026
• DVIDS — RIMPAC 2026 feature — 2026
• U.S. Navy — RIMPAC conclusion — August 3, 2026