Bill Commons

MN HF 4111

died on adjournment

Transit service consolidation in the Twin Cities metropolitan area provided, implementation requirements established, task force established, study required, and reports required.

Minnesota · 2025-2026 · lower

Quick answers

Did MN HF 4111 pass?

No. MN HF 4111 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-03-16): Committee report, to adopt as amended and re-refer to Ways and Means

What is MN HF 4111 about?

MN HF 4111 is a bill in the 2025-2026 titled “Transit service consolidation in the Twin Cities metropolitan area provided, implementation requirements established, task force established, study required, and reports required.”.

Who sponsors MN HF 4111?

Koznick is the primary sponsor of MN HF 4111, joined by 1 cosponsor.

Introduced
2026-03-09
Latest action
2026-03-16 — Committee report, to adopt as amended and re-refer to Ways and Means
Bill type
bill
Last updated

Subjects

Sponsors

  • Koznickprimary
  • Koegelcosponsor

Committees

Not provided by source.

Action timeline

  1. 2026-03-09

    Introduction and first reading, referred to Transportation Finance and Policy

    introduction,referral-committee

  2. 2026-03-12

    Author added Koegel

  3. 2026-03-16

    Committee report, to adopt as amended and re-refer to Ways and Means

    committee-passage

Versions

  • Introduction — 2026-03-06Compare
  • 1st Engrossment — 2026-03-16Compare

Documents

Votes

Not provided by source.

Related bills

Official source

Attribution

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

Inspect retained evidence for changes recorded after evidence tracking began:

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 4111. 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.