Statute of Limitations for Class B / 2nd Degree Felony in Minnesota

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Minnesota, the statute of limitations (often shortened to “SOL”) sets a deadline for the state to file a criminal charge after an alleged offense. For a Class B / 2nd degree felony, Minnesota law uses a general/default limitations period found in Minnesota Statutes § 628.26.

Based on the jurisdiction data you provided, no claim-type-specific sub-rule was found for this charge category. That means this page presents the general rule as the governing baseline rather than a specialized deadline tied to particular felony classifications.

Note: This guide is about the general statute-of-limitations framework in Minnesota. It’s not legal advice, and real cases can turn on additional facts (like investigative delays or procedural events) that may affect when the clock starts, stops, or tolls.

Limitation period

General SOL period: 3 years (default rule)

For the category covered here, the general limitations period is 3 years under Minnesota Statutes § 628.26.

That “3-year” number functions as the starting point for most SOL calculations:

  • Start of the SOL clock: typically tied to the date of the alleged offense (or when the offense is considered complete under Minnesota law).
  • Deadline for charging: the state generally must initiate prosecution within the SOL period.

Because the jurisdiction data indicates no claim-type-specific sub-rule was found, you should treat this 3-year period as the baseline until you validate whether any exception or tolling event applies based on the case record.

How to think about “time window” in practice

When working with SOL deadlines—whether for planning a case review, organizing documents, or preparing a timeline—use a simple approach:

  • Identify the alleged offense date (or the relevant completion date).
  • Count forward 3 years.
  • Then check for events that can extend or pause the SOL under Minnesota exceptions (covered below).

This timeline method helps you quickly spot:

  • When a charge appears time-barred on its face (if the filing date is after the end date), and
  • When further record review is needed because an exception may apply.

Example timeline (illustrative)

If an alleged offense date is January 10, 2023, a 3-year default window would end around January 10, 2026. A prosecution filed after that date would generally be outside the default period—subject to any applicable exceptions or tolling.

Key exceptions

Even when the default rule is a 3-year SOL, Minnesota practice commonly involves questions that can change how that window operates. Under § 628.26, exceptions and doctrines can affect whether the SOL:

  • Starts later than the offense date,
  • Tolls (pauses) during certain periods, or
  • Is otherwise affected by procedural posture.

Because your brief indicates that no charge-category-specific sub-rule was found, the safest practical workflow is:

  • Treat the 3-year period as the default.
  • Then verify whether the case record contains facts that trigger an exception under Minnesota Statutes § 628.26.

Here are concrete “record checkpoints” to look for while building your timeline:

  • Different operative dates

    • Was the charged conduct a course of conduct rather than a single event?
    • Is there a dispute about when the offense was “complete” for SOL purposes?
  • Investigative or procedural events

    • Were there delays tied to motions, warrants, or other procedural steps?
    • Did the case involve an unusual sequence of filings that affects when prosecution was initiated?
  • Allegations involving multiple acts

    • If multiple dates are alleged, confirm which date Minnesota would treat as the relevant starting point for the charge.

Warning: SOL issues often require careful alignment between dates of alleged conduct and the procedural timeline (charging dates, dismissals, refilings, and other events). A correct SOL outcome depends on that fact pattern, not just the headline statute.

If you want to make this process systematic, DocketMath can help you calculate the default deadline first, then you can layer exceptions on top based on the case record.

Statute citation

Minnesota’s general statute of limitations framework for the category addressed here is:

  • Minnesota Statutes § 628.26general/default SOL period of 3 years.

Per your provided jurisdiction data, the general rule is 3 years, and no further claim-type-specific sub-rule was found for this class/degree category. Accordingly, the content here uses § 628.26’s default limitations period as the baseline.

Use the calculator

DocketMath’s statute-of-limitations calculator helps you translate the statute’s deadline into an understandable date you can use for case review.

You can use it here: **/tools/statute-of-limitations

Recommended inputs (what to enter)

To get a useful result, your primary inputs are:

  • Alleged offense date (the date you believe starts the SOL clock under the default rule)
  • Jurisdiction: Minnesota (US-MN)
  • Charge category rule set: use the default 3-year rule based on Minnesota Statutes § 628.26 for this page’s scenario

If your record includes multiple alleged dates, run the calculator once per alleged date so you can compare which counts as the “most conservative” or “most favorable” timeline.

How outputs change with different dates

A statute-of-limitations calculation is date-driven. Here’s what changes when you adjust inputs:

  • Changing the alleged offense date shifts the SOL end date by the same amount forward/backward.
  • Using a different start date (for example, if the offense completion date is disputed) can change the SOL deadline by days, months, or even years.
  • Not accounting for exceptions means the output shows the default deadline only. Any exception or tolling must be checked separately against the case record under § 628.26.

A practical workflow:

  1. Run the calculator with the most clearly supported offense date.
  2. Document the resulting default SOL end date.
  3. Review the file for any exception/tolling indicators tied to Minnesota Statutes § 628.26.
  4. If an exception is plausible, re-check the timeline with the relevant date changes.

Using the tool in your timeline

Once you have the computed end date:

  • Compare it to the charging/commencement date shown in case records.
  • If the charging date is later than the computed end date, you’ve identified a potential time-bar question under the default rule—then you can confirm whether § 628.26 exceptions apply.

Sources and references

Start with the primary authority for Minnesota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading