164th Regiment (United States)
US Army military unit

The 164th Regiment (Regional Training Institute) is a training unit of the North Dakota Army National Guard. As the 164th Infantry Regiment, it was formed during World War I, but traces its history to Dakota Territorial Militia units formed in the 1880s. The regiment was the first United States Army unit to land on Guadalcanal during World War II.
Memorial marker located at ND Veterans Cemetery south of Mandan, ND
History
19th century
The 164th Infantry was originally organized as the 1st Infantry Regiment, Dakota Territorial Militia, in 1885. Upon the admission of North Dakota to the United States in 1889, the regiment was reorganized as the 1st Infantry Regiment, North Dakota National Guard. The regiment was mustered into federal service on 20 May 1898 for service in the Spanish-American War as the 1st North Dakota Volunteer Infantry, and was mustered out on 25 September 1899, resuming its state service.
World War I
The regiment entered federal service on 3 July 1916 for service on the Mexican border, and was stationed at Mercedes, Texas. On 14 February 1917, it was mustered out of service at Fort Snelling, Minnesota. On 5 August 1917, the 1st North Dakota was drafted into federal service, and assigned as an element of the 41st Division. On 4 October 1917, it was redesignated the 164th Infantry Regiment. The 41st Division went to France, but did not see combat and was broken up, with its personnel being reassigned as replacements to frontline units.
“164th Regiment (United States)” enters the record as uS Army military unit. Crown Archives preserves that source wording while asking what 164th, Regiment and United can confirm, complicate or overturn.
Why this record matters
“164th Regiment (United States)” is worth following because a concise public description often conceals a longer documentary argument. Here, 164th, Regiment and United provides the most credible route into that argument.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 31, 2026. The linked authority identifier is Q4551518. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1885, 1889, 1898 and 1899.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. 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 “164th Regiment (United States)”, its source revision and the description used here.
- Expand the search: follow 164th Regiment (United States) primary sources, 164th Regiment (United States) archive and 164th 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 “164th Regiment (United States)”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “164th Regiment (United States)” 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.