Idaho vs North Dakota on USAspending: $1.2B vs $700.4M

Same construction peak, unmatched scale and rows

Idaho and North Dakota share a lead NAICS and do not share a file size. Commercial and institutional building construction leads both, yet Idaho holds $1.2B against $700.4M, 29,667 awards against 7,218, and $80.33 per capita against $63.75. Same mix label, different scale. Cite USAspending.gov.

North Dakota’s 7,218-award construction log is thin next to Idaho’s 29,667-row construction log. Thin is not empty. Row count is not average award size. Do not invent a mean from 29,667 or 7,218.

FY2026 of $160.8M versus $50.8M follows Idaho. Recency agrees with the larger construction-led stock. Treat both amounts as obligation slices. Outlays are omitted. Census counts of 2,001,619 versus 796,568 belong with those ratios on USAspending.gov obligations. Keep both per-capita readings labeled as Census-based packet figures.

A shared construction label is not a matched stock

Commercial and institutional building construction is a first read on both mixes. Use the Idaho and North Dakota state hubs for agencies and recipients. Both peaks are USAspending.gov obligation mixes. Outlays are not listed.

Idaho’s extra people (2,001,619 vs 796,568) help explain the larger $1.2B stock. They do not make the NAICS labels identical work. Mix sameness is not recipient sameness.

FY2026: $160.8M versus $50.8M

Fiscal year 2026 obligations are $160.8M in Idaho and $50.8M in North Dakota. Recency follows Idaho’s larger construction-led file; a shared NAICS does not close FY2026. Treat the year as a recency slice of USAspending.gov obligations, not as Treasury cash already paid.

Do not divide $160.8M or $50.8M by 29,667 or 7,218 all-years awards. Spending per capita of $80.33 and $63.75 already sits beside Census counts of 2,001,619 and 796,568. Cite USAspending.gov for both the stacked stocks ($1.2B vs $700.4M) and the latest-year amounts.

What $80.33 versus $63.75 says on a shared peak

Idaho’s $80.33 is hotter than North Dakota’s $63.75 even on the same construction-family first read. The gap is smaller than Montana-versus-North-Dakota intensity splits, and it still favors Idaho. The $160.8M versus $50.8M FY2026 amounts agree.

Keep every dollar figure labeled as a USAspending.gov obligation. Cite USAspending.gov. Read the shared label as mix, not as a matched ranking.

How to read Idaho versus North Dakota

Read the comparison hub for the tables and the Idaho and North Dakota hubs for agencies and recipients. Stacked stocks are $1.2B versus $700.4M. FY2026 obligations are $160.8M versus $50.8M. Awards are 29,667 versus 7,218. Population is 2,001,619 versus 796,568. Spending per capita is $80.33 versus $63.75. Lead industries are commercial and institutional building construction versus commercial and institutional building construction. Outlays are a different series. Cite USAspending.gov. Keep every dollar figure labeled as an obligation.

Obligations, outlays, and the packet's cuts

Idaho versus North Dakota is a same-industry pair: construction-led files at $1.2B and $700.4M with unmatched award volume of 29,667 versus 7,218. Idaho's packet cuts are $1.2B stacked, $160.8M in FY2026, 29,667 awards, 2,001,619 residents, and $80.33 per capita, with commercial and institutional building construction as the lead NAICS. North Dakota's packet cuts are $700.4M stacked, $50.8M in FY2026, 7,218 awards, 796,568 residents, and $63.75 per capita, with commercial and institutional building construction as the lead NAICS. An obligation is a commitment recorded in USAspending.gov. An outlay is cash paid later and is not in this packet. Do not invent average award size from 29,667 or 7,218. Use the comparison hub for the tables. The Idaho and North Dakota state hubs hold agencies and recipients. Cite USAspending.gov. Keep $80.33 and $63.75 labeled as Census-based obligation ratios. Keep $1.2B and $700.4M labeled as stacked obligation stocks, not as FY2026 cash and not as outlays. Recency slices of $160.8M and $50.8M remain obligation cuts for fiscal year 2026. Population figures are Census counts. commercial and institutional building construction and commercial and institutional building construction remain mix labels, not proofs of a typical award and not substitutes for the stacked ranking of $1.2B versus $700.4M. FY2026 amounts of $160.8M and $50.8M should not be divided by all-years award counts of 29,667 and 7,218. Cite USAspending.gov for the stacked stocks, the latest-year slice, and the Census-based ratios. Keep 29,667 and 7,218 labeled as all-years award totals rather than as FY2026 denominators. Outlays remain unpublished.

Questions

Does Idaho or North Dakota have more federal spending?

Stacked USAspending.gov obligations are $1.2B in Idaho and $700.4M in North Dakota. Spending per capita is $80.33 versus $63.75 on 2,001,619 and 796,568 residents. Award counts are 29,667 versus 7,218. FY2026 obligations are $160.8M in Idaho and $50.8M in North Dakota. Both dollar series are obligations, not outlays.

What industries lead in Idaho and North Dakota?

Idaho's top industry is commercial and institutional building construction. North Dakota's is commercial and institutional building construction. Those labels are the largest NAICS slices on $1.2B and $700.4M. Award counts are 29,667 in Idaho and 7,218 in North Dakota. The rest of each mix sits outside those peaks on USAspending.gov obligation files.

How do Idaho and North Dakota compare on a per-capita basis?

The packet reports $80.33 per capita in Idaho on 2,001,619 residents and $63.75 in North Dakota on 796,568 residents. Stacked stocks are $1.2B versus $700.4M. Award counts are 29,667 versus 7,218. These figures are USAspending.gov obligations, not outlays. FY2026 amounts are $160.8M versus $50.8M.

Are Idaho vs North Dakota figures Treasury outlays?

No. The $1.2B and $700.4M totals, and FY2026 amounts of $160.8M and $50.8M, are USAspending.gov obligations. Outlays are cash payments and can lag behind commitments. Spending per capita ($80.33 vs $63.75) uses Census population where present. This packet does not publish outlays.