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

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In New Hampshire, the statute of limitations (“SOL”) limits how long the state has to bring certain criminal charges after the alleged conduct. For a Class B / 2nd degree felony, the relevant timing question usually starts with the general New Hampshire criminal SOL rule.

DocketMath’s statute-of-limitations calculator is designed to help you compute and visualize that timeline using the core date inputs (e.g., offense date and the assumed filing date). This article focuses on the general/default period because, based on the available jurisdiction data for this topic, no claim-type-specific sub-rule was found for a “Class B / 2nd degree felony” label in New Hampshire. In other words: use the general SOL period unless a specific exception applies.

Note: This is a timing framework for understanding the general rule and how calculations work. It’s not legal advice, and exceptions or specialized doctrines can change outcomes in real cases.

Limitation period

General rule (default)

  • General SOL period: 3 years
  • General statute: RSA 508:4

For classifying the practical takeaway: when people ask, “How long does New Hampshire have to file a felony case that’s categorized as Class B / 2nd degree?” the starting point you’ll typically use is the 3-year general limitation period.

What date should you use?

Most SOL calculations depend on the “event date” and the “filing date”:

  1. Event date (offense date)
    • The day the alleged conduct occurred (or the last date of conduct in a continuing-course scenario).
  2. Filing date (charge/indictment date)
    • The date the charging instrument is filed (or the date the state initiates formal proceedings, depending on context).

When you run a DocketMath calculation, the calculator will use the inputs you provide to produce a “latest filing date” (or a “time remaining / elapsed” view) based on the 3-year general period.

How output changes when inputs change

Use these “what-if” examples to understand the mechanics:

  • If the offense date moves forward by 30 days, the latest permissible filing date generally moves forward by about 30 days (because the SOL is measured in calendar time).
  • If the filing date moves later, the calculation may shift from “within SOL” to “outside SOL,” depending on whether the filing date passes the computed deadline.
  • If you adjust the assumed event date (for instance, the last date of an alleged ongoing act), the deadline will shift accordingly—potentially by months.

Key exceptions

Even where the general period is 3 years, SOL analysis often turns on whether an exception changes timing. Because SOL doctrine can be fact-specific, treat exceptions as “branches” that may alter the endpoint your calculator predicts.

Below are the types of exceptions that commonly arise in SOL conversations (without assuming any particular exception applies automatically to your situation):

1) Tolling (pauses that extend the deadline)

Tolling can effectively “stop the clock” for a portion of time, extending the computed expiration date. Tolling may be triggered by circumstances such as:

  • certain delays attributable to the defendant,
  • certain procedural events,
  • or specific statutory conditions.

If tolling applies, the DocketMath base calculation (3 years) becomes a starting estimate, not the final answer.

2) Discovery-related doctrines (when the “clock” doesn’t start immediately)

Some statutes or doctrines tie the start of the SOL period to a discovery event rather than the offense date. In New Hampshire criminal timing analysis, whether a discovery rule applies depends on the governing statute and the kind of allegation.

3) Procedural posture and “commencement” details

SOL is not only about the length of time; it also matters when proceedings are considered “commenced” for SOL purposes (e.g., filing vs. service vs. other procedural steps). If your filing-related date differs from the date the court treats as “commencement,” results can change.

Warning: If any tolling or “commencement” issue is in play, relying solely on a straight 3-year count can produce an incorrect deadline. Use DocketMath to model the baseline, then account for exceptions only if they’re supported by the facts and governing rules.

4) Multiple acts / continuing conduct

If an allegation includes multiple acts over a period (rather than a single date), the “latest relevant act date” can control the timing. That can shift the SOL deadline substantially, even when the general rule stays at 3 years.

Statute citation

New Hampshire’s general statute of limitations for criminal actions is reflected in:

What this means for “Class B / 2nd degree felony” in this guide

Based on the jurisdiction data provided for this topic, no claim-type-specific sub-rule was found. So the guide uses the default 3-year general SOL period under RSA 508:4.

That means your starting point is straightforward:

  • Default SOL: 3 years
  • Applies unless an exception or a different controlling provision changes the calculation

Use the calculator

You can use DocketMath to calculate the SOL deadline under the general/default 3-year rule.

Primary CTA: **/tools/statute-of-limitations

Recommended inputs

To get an accurate, practical output, enter:

  • Event date (offense date): the date the alleged conduct occurred (or last date of a continuing set of conduct)
  • SOL period assumption: set to 3 years for this general rule
  • Filing/charging date: the date you want to test against the deadline

How to read the results

After you run the calculation, DocketMath will typically produce one or more of the following outputs (wording may vary by interface):

  • Computed “latest filing date” based on the 3-year period
  • Whether the filing date is within or beyond SOL
  • Time elapsed / remaining from the event date to the assumed filing date

Input sensitivity checklist

Before relying on the output, quickly sanity-check:

Related reading