Opposition · USPTO

Opposition 91301035

OtherUSPTO

Opposition 91301035 at USPTO between Medtronic Europe Sarl and KyphoCube, LLC, over the mark KYPHOCUBE, filed Aug 14, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 14, 2025
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Medtronic Europe Sarl

Company trademarks
Respondent

KyphoCube, LLC

Timeline

How the case has moved

Dates from the USPTO record and the KYPHOCUBE filing.

  1. KYPHOCUBE filed

    Application 98863845 filed at the USPTO.
  2. Opposition filed

    Medtronic Europe Sarl started opposition 91301035 at USPTO against KYPHOCUBE.
Marks

Marks involved

2 contested marks, 11 marks the challenger relies on.

MarkRoleApplicationOffice
KYPHOCUBEContested98863845USPTO
KYPHOContested98915860USPTO
KYPHONRelied on75792575USPTO
KYPHONRelied on76124590USPTO
KYPHOPAKRelied on76220779USPTO
KYPHONRelied on77145293USPTO
KYPHON XPANDERRelied on77406668USPTO
KYPHON KURVERelied on86214248USPTO
KYPHON VRelied on86350262USPTO
KYPHON EXPRESSRelied on86361574USPTO
KYPHON ASSISTRelied on88820198USPTO
KYPHON VUERelied on97300956USPTO

+1 more marks in this case

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_8cacbc03-fcc2-4f86-8bf7-66c5543a8afa
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8cacbc03-fcc2-4f86-8bf7-66c5543a8afa",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91301035",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-08-14",
  "parties": [
    {
      "name": "Medtronic Europe Sarl",
      "role": "opponent"
    },
    {
      "name": "KyphoCube, LLC",
      "role": "respondent"
    }
  ]
}