MN SF 3825
died on adjournmentRequirement that loaded firearms be stored in locations where persons prohibited from possessing firearms cannot access the firearms
Minnesota · 2025-2026 · upper
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 3825 pass?
No. MN SF 3825 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-04-27): Author added Gustafson
What is MN SF 3825 about?
MN SF 3825 is a bill in the 2025-2026 titled “Requirement that loaded firearms be stored in locations where persons prohibited from possessing firearms cannot access the firearms”.
Who sponsors MN SF 3825?
Limmer is the primary sponsor of MN SF 3825, joined by 3 cosponsors.
- Introduced
- 2026-02-23
- Latest action
- 2026-04-27 — Author added Gustafson
- Bill type
- bill
- Last updated
- —
Subjects
Sponsors
- Limmerprimary
- Kreuncosponsor
- Abelercosponsor
- Gustafsoncosponsor
Committees
Not provided by source.
Action timeline
Newest first
2026-04-27
Author added Gustafson
2026-03-18
Second reading
reading-2
2026-03-18
Comm report: To pass
committee-passage
2026-02-23
Referred to Judiciary and Public Safety
referral-committee
2026-02-23
Introduction and first reading
introduction
Versions
- Introduction — 2026-02-20Compare
Documents
Votes
Not provided by source.
Related bills
- Companion bill: HF 3497
Official source
Attribution
Data from openstates_api_sync, retrieved 2026-10-08T19:49:05.580899Z
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 3825. 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.