Statute of Limitations for Oral Contract in Nevada

5 min read

Published April 8, 2026 • By DocketMath Team

Overview

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

Nevada’s statute of limitations (SOL) for an oral contract claim is 2 years, under NRS § 11.190(3)(d).

For DocketMath purposes, “oral contract” is treated under Nevada’s general/default limitations framework for contract-related actions when a more claim-type-specific sub-rule is not identified. Nevada law provides this baseline 2-year deadline to help you plan timelines and organize documents.

Note: This article explains Nevada’s general/default rule for oral contract claims. If your situation involves a different cause of action (for example, fraud, written contract issues, or another statutory scheme), the SOL may be different. DocketMath’s calculator is best used after you confirm the claim category you’re modeling.

Limitation period

Nevada’s general/default SOL for an oral contract claim is 2 years.

Where the 2-year period comes from

  • Statute: **NRS § 11.190(3)(d)
  • SOL length: 2 years
  • Type of action: This provision supplies the general/default limitations period for certain actions involving obligations tied to contractual relationships, which is the baseline category used for oral-contract disputes when no more specific oral-contract sub-rule is found.

**What “general/default” means here (important)

  • You provided jurisdiction data indicating no claim-type-specific sub-rule was found for oral contracts.
  • That means the 2-year period above is the default starting point for your analysis unless your facts and claim framing clearly point to a different limitation provision.

**When the clock starts (practical modeling) In most SOL calculations, the key step is identifying the relevant accrual/event date—often tied to when the breach occurred or when the claim became actionable (which can depend on the facts).

DocketMath’s workflow helps you:

  • choose an event date (for example, date of breach, date performance ended, or when nonpayment became definite), and
  • generate a deadline using the 2-year SOL baseline.

Checklist for getting your inputs right:

Key exceptions

Even with a 2-year general SOL under NRS § 11.190(3)(d), deadlines can shift due to how courts determine accrual and whether any legally recognized doctrines affect timing. Because these are fact-dependent, treat the items below as watch areas, not automatic adjustments.

1) Accrual and “event date” disputes

If parties disagree about when the claim accrued, the SOL deadline can change. Common areas of disagreement include:

  • when performance was due,
  • when nonperformance became clear,
  • when damages became ascertainable in a way that triggers accrual for the claim.

Action step: build a dated timeline (agreement date, performance milestones, payment due dates, and the first date performance/nonpayment became definite).

2) Tolling (pauses in the SOL clock)

Some legal circumstances can pause (toll) limitations periods. Tolling depends on the specific legal basis and often requires meeting certain conditions.

Warning: tolling is not automatic. If your matter involves special proceedings or statutory tolling triggers, you’ll want to map the facts carefully before assuming the deadline is extended.

3) Different claim type → different SOL

The 2-year default may not apply if the dispute is framed as a different type of claim. For example:

  • a statutory cause of action with its own limitations period,
  • claims that functionally fit a different legal theory than “oral contract,”
  • disputes involving written instruments that change the nature of the contractual obligations.

Action step: match the cause of action label to the statute you intend to apply. Once the category is confirmed, DocketMath can compute the deadline.

4) Procedural timing effects (filing vs. service)

SOL analysis can be affected by procedural timing questions—what counts as “filed,” how rules interact with deadlines, and case posture. Even when the SOL “deadline date” is known, procedural details can still matter.

Practical approach: treat the SOL date as a latest-file-by target, not a last-minute filing plan.

Pitfall: Using the 2-year SOL without verifying the accrual/event date can produce an incorrect deadline. For DocketMath calculations, accuracy about the event date you choose is as important as the statute.

Statute citation

NRS § 11.190(3)(d) — Nevada’s general SOL provision setting a 2-year limitations period for certain actions, including the general/default period used here for oral-contract claims in the absence of a more specific sub-rule.

Source: https://law.justia.com/codes/nevada/chapter-11/statute-11-190/

Use the calculator

DocketMath’s statute-of-limitations calculator converts the 2-year rule into a specific deadline using dates from your timeline.

Primary CTA: /tools/statute-of-limitations

How to use it effectively

  1. Select jurisdiction: Nevada (US-NV).
  2. Select claim model: oral contract (default 2-year) under NRS § 11.190(3)(d).
  3. Enter the key date: provide the accrual/event date you’re using for the SOL analysis.
  4. Review the output: the tool calculates the latest deadline based on 2 years from your chosen date.

How the output changes with inputs

  • If you input a later event/accrual date, the SOL deadline shifts later by roughly the same amount.
  • If you input an earlier event/accrual date, the deadline tightens accordingly.
  • Because accrual can be contested, the calculator is most useful when your chosen event date is supported by your timeline and facts.

Quick date example (for modeling only, not legal advice):

  • If the breach/nonpayment became definite on June 1, 2023, then a 2-year baseline deadline would fall around June 1, 2025—subject to (1) how you justify the accrual/event date and (2) any legally recognized timing adjustments you may need to evaluate.

Checklist before relying on the computed date:

Related reading