Opposition · USPTO

Opposition 91288950

OtherUSPTO

Opposition 91288950 at USPTO between Fuente Marketing Ltd. and Magellan Technology Inc., over the mark MTRX, filed Dec 27, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 27, 2023
Marks involved
26
Parties

Who is involved

The parties as named in the office record.

Opponent

Fuente Marketing Ltd.

Respondent

Magellan Technology Inc.

Timeline

How the case has moved

Dates from the USPTO record and the MTRX filing.

  1. MTRX filed

    Application 97903163 filed at the USPTO.
  2. Opposition filed

    Fuente Marketing Ltd. started opposition 91288950 at USPTO against MTRX.
Marks

Marks involved

1 contested mark, 25 marks the challenger relies on.

MarkRoleApplicationOffice
MTRXContested97903163USPTO
FUENTE FUENTE OPUS "X"Relied on74550044USPTO
FUENTE OPUS XRelied on75030336USPTO
FUENTE OPUS X FFRelied on75069035USPTO
XRelied on75749265USPTO
FUENTE OPUSXRelied on75857912USPTO
X TO THE THIRD POWERRelied on75859380USPTO
FORBIDDENXRelied on75982386USPTO
XRelied on76290310USPTO
XRelied on77064649USPTO
FUENTE FUENTE OPUSXRelied on77612116USPTO
FFOXRelied on77815008USPTO

+14 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_69a52575-a6e3-45da-b73c-58da8394a25c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_69a52575-a6e3-45da-b73c-58da8394a25c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91288950",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-12-27",
  "parties": [
    {
      "name": "Fuente Marketing Ltd.",
      "role": "opponent"
    },
    {
      "name": "Magellan Technology Inc.",
      "role": "respondent"
    }
  ]
}