Opposition · USPTO

Opposition 91249596

OtherUSPTO

Opposition 91249596 at USPTO between Arm Limited and CKL Holdings N.V., over the mark ARMADA, filed Jul 17, 2019. Status in the office record: other.

View ARMADAGet this data via the API
Status
Other
Result
Other
Filed
Jul 17, 2019
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Arm Limited

Company trademarks
Respondent

CKL Holdings N.V.

Timeline

How the case has moved

Dates from the USPTO record and the ARMADA filing.

  1. ARMADA filed

    Application 87365897 filed at the USPTO.

  2. Opposition filed

    Arm Limited started opposition 91249596 at USPTO against ARMADA.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
ARMADAContested87365897USPTO
ARM7TDMIRelied on75713153USPTO
ARMRelied on75713155USPTO
ARMRelied on75713156USPTO
ARMRelied on75713165USPTO
ARM POWEREDRelied on75750700USPTO
ARM POWEREDRelied on75750721USPTO
ARM7TDMIRelied on75750726USPTO
ARM POWEREDRelied on76139898USPTO
ARM POWEREDRelied on76298758USPTO
ARM CONNECTEDRelied on77542728USPTO
ARM7TDMIRelied on86390868USPTO

+3 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_30bce541-a81a-4d91-9f2e-0ca3981073d3
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_30bce541-a81a-4d91-9f2e-0ca3981073d3",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91249596",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-07-17",
  "parties": [
    {
      "name": "Arm Limited",
      "role": "opponent"
    },
    {
      "name": "CKL Holdings N.V.",
      "role": "respondent"
    }
  ]
}