Battle of Oktwin
Open-knowledge reference entry

The Battle of Oktwin was the second battle in the Battle of Yunnan-Burma Road in the Burma campaign of World War II and Second Sino-Japanese War.
On March 20, the Japanese 143rd Regiment plus cavalry units of the 55th Division attacked the positions of the Chinese 5th Army Cavalry Regiment north of the Kan River, driving the Chinese forces back with heavy losses. The bulk of the cavalry regiment was withdrawn to the north of Toungoo, leaving only a company of cavalry and infantry each to delay the advancing Japanese. Meanwhile, the commanding general of 200th Division, Dai Anlan's fortifications at Oktwin and around Toungoo were now ready. They were built using timber, which was in abundant supply, and all positions were carefully concealed. On March 21, Japanese forces brushed aside the delaying forces and reached the 200th Division outposts at Oktwin.
The 112th Regiment of the 55th Division attacked 200th Division positions at first light on March 22, but made little headway. Japanese forces attacking the Chinese positions consisted of a battalion of infantry with several guns; the defenders were the 1st Battalion, 600th Regiment. The Japanese sent cavalry forces around the left flank of the Chinese and the position was stabilized only when reserve forces of the 1st Battalion, 598th Regiment were committed immediately in counterattacks.
The Japanese were now more careful after the ambush, and used their artillery and machine guns to fire at suspected positions before sending their infantry forward.
This brief starts where responsible research should: with the source description of “Battle of Oktwin” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 21, 2026. The linked authority identifier is Q4871936. Authority coordinates are 18.829, 96.405. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Battle of Oktwin”, its source revision and the description used here.
- Expand the search: follow Battle of Oktwin primary sources, Battle of Oktwin archive and Battle research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Battle of Oktwin”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Battle of Oktwin” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.