Opposition · USPTO

Opposition 91237715

OtherUSPTO

Opposition 91237715 at USPTO between IMAX Corporation and Pimax Technology (Shanghai) Co., Ltd, over the mark PIMAX, filed Oct 6, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 6, 2017
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

IMAX Corporation

Respondent

Pimax Technology (Shanghai) Co., Ltd

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the PIMAX filing.

  1. PIMAX filed

    Application 86967143 filed at the USPTO.
  2. Opposition filed

    IMAX Corporation started opposition 91237715 at USPTO against PIMAX.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
PIMAXContested86967143USPTO
IMAXRelied on72356735USPTO
IMAXRelied on73388162USPTO
MOVIES TO THE MAXRelied on74073899USPTO
IMAXRelied on75131600USPTO
THE IMAX EXPERIENCERelied on75230700USPTO
AN IMAX EXPERIENCERelied on75497758USPTO
TO THE MAXRelied on75840741USPTO
IMAX DMRRelied on76532215USPTO
AT THE MAXRelied on76632397USPTO
IMAXRelied on85135280USPTO
IMAX VRRelied on87104709USPTO
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_aa6e9d3a-e82e-494d-b0c3-118ac66856c5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_aa6e9d3a-e82e-494d-b0c3-118ac66856c5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91237715",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-10-06",
  "parties": [
    {
      "name": "IMAX Corporation",
      "role": "opponent"
    },
    {
      "name": "Pimax Technology (Shanghai) Co., Ltd",
      "role": "respondent"
    }
  ]
}