Bill Commons

MN SF 4326

died on adjournment

Certain Twin Cities metropolitan area transit service consolidation provisions, implementation requirements establishment, and Transit Consolidation Task Force establishment

Minnesota · 2025-2026 · upper

Follow this bill’s action updates (Atom)

Subscribe in a feed reader. The feed covers recorded actions from the last 30 days; Bill Commons may record an action after it happened at the legislature.

Quick answers

Did MN SF 4326 pass?

No. MN SF 4326 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-18): Author stricken Rarick

What is MN SF 4326 about?

MN SF 4326 is a bill in the 2025-2026 titled “Certain Twin Cities metropolitan area transit service consolidation provisions, implementation requirements establishment, and Transit Consolidation Task Force establishment”.

Who sponsors MN SF 4326?

Hoffman is the primary sponsor of MN SF 4326.

Introduced
2026-03-11
Latest action
2026-03-18 — Author stricken Rarick
Bill type
bill
Last updated
—

Subjects

Sponsors

  • Hoffmanprimary

Committees

Not provided by source.

Action timeline

Newest first

  1. 2026-03-18

    Author stricken Rarick

  2. 2026-03-17

    Authors stricken Abeler; Housley; Maye Quade

  3. 2026-03-11

    Referred to Transportation

    referral-committee

  4. 2026-03-11

    Introduction and first reading

    introduction

Versions

Documents

Votes

Not provided by source.

Related bills

Official source

Attribution

Data from openstates_api_sync, retrieved 2026-10-09T02:46:41.165798Z

Inspect retained evidence for changes recorded after evidence tracking began:

Session-wide evidence can include changes to other bills:

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=SF 4326. 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.