Statute of Limitations for Class C / Petty Misdemeanor in North Dakota

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In North Dakota, the time limits for charging and prosecuting certain lower-level criminal offenses are governed by statute. For Class C misdemeanors—often described in practice as “petty misdemeanor”-level conduct—the relevant statute of limitations is typically measured in months from the date the alleged offense occurred.

This matters because the state generally must file or initiate prosecution within the limitation period. If the deadline passes, defendants can raise the limitations issue to seek dismissal (procedure varies by case posture). This page is designed to help you identify the governing limitation period and common factors that can affect it, using DocketMath’s statute-of-limitations calculator to model dates.

Note: Statute of limitations rules can be affected by specific procedural events (for example, service, filing, or certain tolling circumstances). Use the calculator for a baseline timeline, then confirm how the relevant dates map to the case record.

Limitation period

For Class C misdemeanors / petty misdemeanor offenses in North Dakota, the statute of limitations is 12 months (1 year).

What “12 months” usually means in practice

  • The clock generally starts on the date of the alleged offense.
  • The limiting issue is whether prosecution is commenced (not merely investigated) within the period.
  • The period is short, so even small date differences—weeks or months—can be outcome-determinative.

Common timeline check (example)

If an alleged Class C misdemeanor occurred on:

  • January 10, 2025, a baseline 12-month deadline would fall on/around January 10, 2026.
  • If the prosecution is initiated after the deadline, the limitations defense may apply.

Because the exact legal meaning of “commenced” depends on North Dakota criminal procedure and the case’s specific filings, treat the calculator result as a date-to-date screening tool, not a final determination.

Inputs you’ll use in DocketMath

When you use DocketMath’s statute-of-limitations calculator (link below), you’ll typically provide:

  • Offense date (the date the conduct is alleged to have occurred)
  • Offense type (select the misdemeanors class category relevant to Class C / petty misdemeanor)
  • Optionally, other date inputs depending on the calculator’s design (for example, an event date such as filing or issuance of process)

How outputs change based on inputs

In a 12-month limitations regime:

  • Later offense dates push the deadline later by the same amount of time.
  • Earlier offense dates move the deadline earlier.
  • If you enter a case event date (such as a filing date) into the calculator, the output typically indicates whether that date is before or after the calculated deadline.

Key exceptions

North Dakota limitations analysis doesn’t always stop at a straight “date plus 12 months” calculation. Several categories of exceptions can change the outcome by altering the timeline—either by tolling (pausing) or by changing when the state is deemed to have acted in a way that satisfies the statute.

1) Tolling and “clock-pausing” events

Some events can pause the limitations clock or affect when it begins to run. Common tolling concepts in criminal cases can include:

  • Defendant conduct that makes it impossible or impracticable to proceed
  • Procedural delays caused by specific legal events
  • Situations where the defendant’s whereabouts or availability affects prosecution

Because tolling is fact- and procedure-specific, your case may not fit a simple “always 12 months” model.

Pitfall: People often compute “offense date + 12 months” and stop there. If the prosecution initiated within that period, you still need to match the case event that counts under North Dakota procedure—while tolling may shift what “within the period” means.

2) When prosecution is “commenced”

Even when the limitation period length is clear, the legal question can be whether the state has commenced prosecution in a way recognized by statute. This depends on North Dakota’s criminal procedure mechanics, including how and when charges are filed and how process is handled.

3) Classification matters (Class C vs. other misdemeanors)

The 12-month period is tied to Class C misdemeanors. If the alleged offense is actually classified differently (e.g., Class A, B, or an infraction), the statute of limitations period may be different.

A practical way to avoid mistakes:

  • Use the charging documents (or the specific statutory classification) to confirm the class used for the alleged conduct.
  • Then apply the corresponding limitations period.

Statute citation

The statute of limitations for Class C misdemeanors in North Dakota is set out in N.D. Cent. Code § 29-04-02.

For Class C misdemeanors / petty misdemeanor-level offenses, the limitation period is twelve months (1 year) under that statute.

Use the calculator

Use DocketMath’s statute-of-limitations tool to convert dates into a deadline quickly and consistently. Start here:

What to do step-by-step

  1. Open the calculator at /tools/statute-of-limitations.
  2. Select North Dakota (US-ND).
  3. Choose the offense category corresponding to Class C / petty misdemeanor.
  4. Enter the offense date.
  5. If the calculator includes an event date field, enter the date of filing/charging/prosecution initiation (use the date the case record identifies as the relevant initiation date).

How to interpret the result

  • If your entered event date is before the calculated deadline, the prosecution is typically treated as timely under the baseline 12-month period.
  • If it is after the deadline, it may be barred—subject to the possibility of exceptions/tolling and the “commenced prosecution” mechanics.

Because real cases involve procedural events not captured by a simple date input, treat the output as a timeline screen rather than a final legal conclusion.

Sources and references

Start with the primary authority for North Dakota 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