Opposition · USPTO

Opposition 91303410

PendingUSPTO

Opposition 91303410 at USPTO between Spartan Race, Inc. and Sparta Beverage LLC, over the mark SPARTAN ENERGY, filed Nov 27, 2025. Status in the office record: pending.

Status
Pending
Filed
Nov 27, 2025
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Spartan Race, Inc.

Company trademarks
Respondent

Sparta Beverage LLC

Timeline

How the case has moved

Dates from the USPTO record and the SPARTAN ENERGY filing.

  1. SPARTAN ENERGY filed

    Application 97101217 filed at the USPTO.
  2. Opposition filed

    Spartan Race, Inc. started opposition 91303410 at USPTO against SPARTAN ENERGY.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
SPARTAN ENERGYContested97101217USPTO
SPARTANRelied on77109515USPTO
SPARTANRelied on77636892USPTO
SPARTAN RACERelied on85076958USPTO
SPARTAN TRAININGRelied on85845532USPTO
SPARTANRelied on87087553USPTO
SPARTANRelied on87087556USPTO
SPARTANRelied on87802975USPTO
SPARTANRelied on88309363USPTO
SPARTANRelied on90175184USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_f5673786-ffce-4433-a735-628e32a3a78a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f5673786-ffce-4433-a735-628e32a3a78a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91303410",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2025-11-27",
  "parties": [
    {
      "name": "Spartan Race, Inc.",
      "role": "opponent"
    },
    {
      "name": "Sparta Beverage LLC",
      "role": "respondent"
    }
  ]
}