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

A 36,000-row services log against 7,218 construction awards

Nebraska and North Dakota share a regional neighborhood and almost nothing else in this packet. Nebraska’s services peak sits on $1.2B, 36,000 awards, $175.68 per capita, and $352.3M in FY2026. North Dakota’s construction peak sits on $700.4M, 7,218 awards, $63.75 per capita, and $50.8M. Cite USAspending.gov.

Award volume of 36,000 versus 7,218 is one of the wider row gaps among neighboring pairs. The thinner construction log still posts $700.4M. It does not match Nebraska’s services file. Row count is not average award size. Do not invent a mean from 36,000 or 7,218.

FY2026 of $352.3M versus $50.8M is a recency cliff. Treat both amounts as obligation slices. Outlays are omitted. Census counts of 2,005,465 versus 796,568 belong with the $175.68 and $63.75 readings on USAspending.gov obligations.

Other computer related services versus building construction

Those NAICS peaks are first reads on $1.2B and $700.4M. Use the Nebraska and North Dakota state hubs for agencies and recipients. Both peaks are USAspending.gov obligation mixes. Outlays are not listed.

Neighbor status does not merge a services mix with a construction mix. North Dakota’s 7,218 awards include many actions outside building construction. Nebraska’s 36,000 awards extend beyond computer related services.

FY2026: $352.3M versus $50.8M

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

Do not divide $352.3M or $50.8M by 36,000 or 7,218 all-years awards. Spending per capita of $175.68 and $63.75 already sits beside Census counts of 2,005,465 and 796,568. Cite USAspending.gov for both the stacked stocks ($1.2B vs $700.4M) and the latest-year amounts.

Construction dollars on a cooler Dakota ratio

North Dakota’s $63.75 on 796,568 residents is cooler than Nebraska’s $175.68. A smaller Census count does not heat the ratio here. The construction peak sits on that cooler reading and on the $50.8M FY2026 slice.

Nebraska’s services-led $1.2B file remains larger on stacked dollars, intensity, awards, and recency. Cite USAspending.gov. Keep every dollar figure labeled as an obligation.

How to read Nebraska versus North Dakota

Read the comparison hub for the tables and the Nebraska and North Dakota hubs for agencies and recipients. Stacked stocks are $1.2B versus $700.4M. FY2026 obligations are $352.3M versus $50.8M. Awards are 36,000 versus 7,218. Population is 2,005,465 versus 796,568. Spending per capita is $175.68 versus $63.75. Lead industries are other computer related services 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

Nebraska versus North Dakota is a neighbors pair split by mix and intensity: services at $175.68 on $1.2B against construction at $63.75 on $700.4M. Nebraska's packet cuts are $1.2B stacked, $352.3M in FY2026, 36,000 awards, 2,005,465 residents, and $175.68 per capita, with other computer related services 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 36,000 or 7,218. Use the comparison hub for the tables. The Nebraska and North Dakota state hubs hold agencies and recipients. Cite USAspending.gov. Keep $175.68 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 $352.3M and $50.8M remain obligation cuts for fiscal year 2026. Population figures are Census counts. other computer related services 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 $352.3M and $50.8M should not be divided by all-years award counts of 36,000 and 7,218. Cite USAspending.gov for the stacked stocks, the latest-year slice, and the Census-based ratios. Keep 36,000 and 7,218 labeled as all-years award totals rather than as FY2026 denominators. Outlays remain unpublished.

Questions

Does Nebraska or North Dakota have more federal spending?

Stacked USAspending.gov obligations are $1.2B in Nebraska and $700.4M in North Dakota. Spending per capita is $175.68 versus $63.75 on 2,005,465 and 796,568 residents. Award counts are 36,000 versus 7,218. FY2026 obligations are $352.3M in Nebraska and $50.8M in North Dakota. Both dollar series are obligations, not outlays.

What industries lead in Nebraska and North Dakota?

Nebraska's top industry is other computer related services. 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 36,000 in Nebraska and 7,218 in North Dakota. The rest of each mix sits outside those peaks on USAspending.gov obligation files.

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

The packet reports $175.68 per capita in Nebraska on 2,005,465 residents and $63.75 in North Dakota on 796,568 residents. Stacked stocks are $1.2B versus $700.4M. Award counts are 36,000 versus 7,218. These figures are USAspending.gov obligations, not outlays. FY2026 amounts are $352.3M versus $50.8M.

Are Nebraska vs North Dakota figures Treasury outlays?

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