MN HF 3176

died on adjournment

Rail corridor service analysis required for passenger rail service to Fargo and Kansas City, commissioner of transportation required to apply for federal passenger rail corridor identification and development programming, and money appropriated.

Minnesota · 2025-2026 · lower

Quick answers

Did MN HF 3176 pass?

No. MN HF 3176 died when the 2025-2026 session adjourned without final action on it. Bills that die this way are sometimes reintroduced in a later session. Latest recorded action (2026-05-13): Author added Jones

What is MN HF 3176 about?

MN HF 3176 is a bill in the 2025-2026 titled “Rail corridor service analysis required for passenger rail service to Fargo and Kansas City, commissioner of transportation required to apply for federal passenger rail corridor identification and development programming, and money appropriated.”.

Who sponsors MN HF 3176?

Koegel is the primary sponsor of MN HF 3176, joined by 4 cosponsors.

Introduced: 2025-04-10
Latest action: 2026-05-13 — Author added Jones
Bill type: bill
Last updated: —

Subjects

Committees

Not provided by source.

Action timeline

2025-04-10
Introduction and first reading, referred to Transportation Finance and Policy
introduction,referral-committee
2025-04-22
Author added Kraft
2026-02-17
Author added Greene
2026-03-18
Author added Pursell
2026-05-13
Author added Jones

Versions

Introduction — 2025-04-10Compare

Documents

text/html

Votes

Not provided by source.

Related bills

Companion bill: SF 2887

Official source

https://www.revisor.mn.gov/bills/94/2025/0/HF/3176?list=open&body=House

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:24:48.331508Z

Inspect retained evidence for changes recorded after evidence tracking began:

Source and document changes Status and relationship changes

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=MN&identifier=HF 3176. See the API docs or the MCP server for AI assistants.

Known limitations

Sponsor party and chamber affiliation are not yet captured by this API.
Committee referrals are not yet captured.

See the methodology page for data sources and limitations.