Statute of Limitations for Class B Misdemeanor in Texas

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In Texas criminal cases, the statute of limitations (SOL) sets a deadline for the state to start a prosecution for an offense. For a Class B misdemeanor, that deadline comes from the general limitations framework in the Texas Code of Criminal Procedure, Chapter 12.

DocketMath’s statute-of-limitations calculator helps you convert Texas’s time rules into a plain “last day to file” style result. This article focuses on the general/default rule for limitations in Chapter 12 because no Class B–specific sub-rule was found in the available jurisdiction data you provided.

Note: This page explains the general limitations rule for misdemeanors under Chapter 12. It does not attempt to cover every possible fact pattern (for example, cases involving tolling events). Use the calculator and then verify the result against the specific case timeline.

Limitation period

Default SOL period for a Class B misdemeanor (Texas)

Texas’s general SOL period for this category, based on the provided jurisdiction data, is:

  • General SOL Period: 0.0833333333 years

Converting that to days:

  • 0.0833333333 years ≈ 1/12 of a year
  • 1/12 of 365 days ≈ 30.4 days

In practice, Texas limitations deadlines are often expressed in months or years by statute, so the calculator will present the output in a concrete calendar form based on the start date you provide.

Because the jurisdiction data is expressed in years, the calculator is useful for turning that fraction into an actual end date you can work with.

Inputs that change the output

To get an accurate SOL “deadline” date, DocketMath needs at least one core date (and sometimes additional dates depending on the tool setup). Common inputs include:

  • Date of the offense (the usual starting point)
  • Relevant case dates (only if you want to model tolling or later procedural events)
  • Jurisdiction (US-TX is already set for this calculator page, but it affects the rule selection)

What changes the result most:

  • Offense date: the entire SOL window shifts forward or backward.
  • Whether you model exceptions/tolling: certain events can pause or extend the limitations period. If you don’t model them, the output reflects the default running clock only.

Quick example (default rule only)

If you enter:

  • Offense date: January 15, 2025

Then the calculator’s default window (based on the general Chapter 12 period provided) produces an SOL “run-date” about 30 days after the offense date (the exact calendar date depends on how the tool rounds/converts to a specific day count).

Again, that’s the default. If the state argues that an exception applies, your deadline may move.

Key exceptions

Texas limitations rules can be affected by exceptions that pause, extend, or otherwise alter the default running of the clock. Since your provided note states that no Class B–specific sub-rule was found, the safe way to think about “exceptions” here is:

  • Default period runs unless an exception/tolling event applies.
  • Some exceptions are fact-driven and can depend on what happened between the offense and the filing or issuance of process.

Common categories of exception behavior to look for

Without giving legal advice, here are practical checkpoints people usually verify when a limitations issue is raised:

  • Tolling/pause events: events that stop the limitations clock from running during a defined period.
  • “Commencement” timing: limitations may depend on when prosecution is deemed to have started (often linked to filing/issuance concepts rather than when investigators began working).
  • Procedural delays attributable to the defendant or case posture: in some systems, certain delays can affect the limitations analysis.
  • Multiple offenses or amended charges: amendments may raise timing questions.

Warning: A limitations calculation using only the offense date and the default SOL period can be wrong if there was tolling or a key procedural event that changes when the clock stops/starts.

How to use DocketMath when exceptions might exist

If your timeline suggests something unusual occurred, treat DocketMath as a baseline calculator, not a final legal conclusion. A practical workflow:

  • Step 1: Compute the default SOL deadline from the offense date.
  • Step 2: Identify any timeline events that could affect running time.
  • Step 3: Re-run the calculator using those dates or toggles (if the tool supports them).
  • Step 4: Compare the tool’s output to the actual filing/charging milestone you care about.

If the recalculated deadline differs from the default, you’ve learned where exceptions (or at least additional facts) may matter.

Statute citation

The controlling framework referenced for this SOL calculation is:

DocketMath’s rule selection on this page uses the general/default period indicated by the jurisdiction data you provided:

  • General SOL Period: 0.0833333333 years
  • Interpretation in this article: a default limitations window derived from Chapter 12’s general limitations rule applicable under the assumptions stated above.

Use the calculator

Use DocketMath’s statute-of-limitations tool to turn the default limitations window into a concrete deadline date for Texas.

Primary CTA: /tools/statute-of-limitations

What to enter

In the DocketMath calculator, you’ll generally provide:

  • Offense date (required for the deadline computation)
  • Optional dates if you want to explore how the result changes with additional timeline factors

If you’re unsure which optional fields apply, start with the offense date only. That gives you the default ending point.

How output changes with your inputs

Here’s the practical effect:

Input you changeWhat happens to the deadline
Offense dateThe SOL deadline shifts accordingly (the clock starts over).
Adding exception/tolling dates (if supported)The clock may pause or extend, moving the deadline later.
Using default-only modeOutput reflects the general/default period and will not account for tolling.

If you only take one action from this page, do this:

  • Run default-only first.
  • Then, if the case timeline includes anything that looks like a pause/exception, run again with those dates (or otherwise reconcile the timeline with Chapter 12’s exception rules).

Related reading