Tolling the statute of limitations in Minnesota

Direct answer

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In Minnesota, the general statute of limitations (SOL) is 3 years for many covered non-felony criminal matters, governed by Minn. Stat. § 628.26. Tolling (pausing or extending that deadline) generally depends on specific, recognized events under Minnesota law—so tolling does not happen automatically just because time passed.

If you’re trying to estimate when the SOL expires and whether the period was paused or extended, use DocketMath’s statute-of-limitations calculator (jurisdiction: US-MN) to model the timeline using Minnesota’s general 3-year baseline from Minn. Stat. § 628.26 and any tolling dates you have.

What you need to know

Tolling changes the SOL end date by adding time or pausing the clock—but only if the underlying legal trigger applies. In practice, you’ll usually be working with these timeline dates:

• Accrual / offense date: when the charged conduct (or relevant event) occurred.
• Filing date: when the charging document/complaint was filed.
• Tolling trigger date(s): dates tied to a tolling event the parties argue under Minnesota law.

DocketMath helps you model how the clock changes by letting you enter:

• the clock start date,
• the filing date you’re testing, and
• any tolling start/end dates (if the tool supports a pause window or added time inputs).

How to think about tolling (practically)

Start with a reliable baseline first, then apply tolling only when you can identify:

1. What the tolling event was,
2. When it started, and (if applicable)
3. When it ended or how long it affects the clock.

If your inputs don’t match the legal characterization (for example, treating a pause as an extension), the computed “timely vs. untimely” result can flip.

Step-by-step

Follow these steps to model Minnesota SOL tolling using DocketMath and Minn. Stat. § 628.26 (general SOL: 3 years).

1) Lock in the baseline SOL period

Use the general/default period:

• General SOL Period: 3 years
• General Statute: Minn. Stat. § 628.26
• Baseline used here: The default 3-year rule (no claim-type-specific sub-rule provided in the materials).

2) Identify the clock start (offense/relevant conduct) date

For many SOL timelines, the clock start is tied to the offense date (or the date conduct is tied to the charge).

Input to gather:

• Offense / clock start date: YYYY-MM-DD

3) Identify the filing date you’re testing

This is the date the charge/complaint was filed in Minnesota.

Input to gather:

• Filing date: YYYY-MM-DD

4) Gather tolling trigger details (only if you have them)

Tolling generally requires specific asserted events with supporting dates. This guide won’t invent tolling theories; it gives you a consistent way to apply the dates you have.

Inputs to gather (as applicable):

• Tolling start date: YYYY-MM-DD
• Tolling end date: YYYY-MM-DD (if the asserted theory is a pause window)

If you don’t know the tolling trigger dates, you can still run the baseline calculation, then revisit tolling once the record identifies the relevant event dates.

5) Run the numbers in DocketMath

Open DocketMath’s statute-of-limitations tool here:

• /tools/statute-of-limitations

Set:

• Jurisdiction: **US-MN (Minnesota)

Then enter:

• the clock start/offense date
• the filing date
• the tolling dates (if the tool prompts for them)

Review the outputs for:

• the baseline SOL deadline (no tolling), and
• the adjusted SOL deadline (with tolling applied per your inputs)

Finally, compare:

• filing date ≤ adjusted deadline → likely timely under that model
• filing date > adjusted deadline → likely untimely under that model

6) Validate the timeline against the underlying record

Before relying on the result, sanity-check:

• Are the dates in the format the tool expects?
• Does your “clock start” date reflect the charged conduct you’re using?
• Are the tolling start/end dates consistent with how the event is described in the record?

Caution (not legal advice): SOL tolling outcomes can turn on legal characterization (e.g., whether a doctrine truly pauses time). If the event is misclassified, the date math may produce a misleading result—even if the entered dates are correct.

Key statutes and citations

This guide uses the Minnesota general SOL baseline and then models tolling using the dates you provide.

Minnesota court-records context (informational):

• https://minnesotacourtrecords.us/criminal-court-records/gross-misdemeanor/

Tool link (use for calculations):

• /tools/statute-of-limitations

Common pitfalls

• Using the wrong baseline SOL

  • This article uses 3 years under Minn. Stat. § 628.26 because that’s the general default provided. If your matter falls outside the general/default category, the baseline may change.

• Assuming tolling automatically applies

  • Tolling typically depends on specific events. No event, no tolling—at least not in a model grounded in recognized legal triggers.

• Swapping key dates

  • If you input the offense date where the tool expects a different start date (or vice versa), the deadline shifts in the wrong direction.

• Mixing “pause windows” with “one-time extensions”

  • Some tolling approaches effectively add time, while others pause the running clock. Use the correct date structure (start/end vs. added-time inputs) supported by the tool and your asserted theory.

• Not comparing the adjusted deadline to the filing date

  • Always do the “before/after” comparison based on the tool’s baseline vs. adjusted outputs.

Run the numbers

DocketMath’s statute-of-limitations calculator supports the workflow: enter the clock start date, the filing date, and tolling dates (if applicable), then compare deadlines.

Below are common input patterns using the 3-year baseline under Minn. Stat. § 628.26:

What to do next

1. Go to /tools/statute-of-limitations
2. Set Jurisdiction: US-MN
3. Use the 3-year baseline consistent with Minn. Stat. § 628.26
4. Enter:

   • Offense / clock start date
   • Filing date
   • Tolling dates (only if you have them and they align with your asserted tolling basis)

Then focus on two results:

• baseline deadline
• adjusted deadline
  …and compare each to the filing date.

Related reading

• Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
• Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
• Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator