Opposition · USPTO

Opposition 91242458

OtherUSPTO

Opposition 91242458 at USPTO between Fca Us LLC and Shenzhen Gudsen Intelligent Technology Co., Ltd., over the mark MOKAR, filed Jul 17, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 17, 2018
Marks involved
23
Parties

Who is involved

The parties as named in the office record.

Opponent

Fca Us LLC

Company trademarks
Respondent

Shenzhen Gudsen Intelligent Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the MOKAR filing.

  1. MOKAR filed

    Application 87266140 filed at the USPTO.
  2. Opposition filed

    Fca Us LLC started opposition 91242458 at USPTO against MOKAR.
Marks

Marks involved

2 contested marks, 21 marks the challenger relies on.

MarkRoleApplicationOffice
MOKARContested87266140USPTO
MOKARContested87266149USPTO
MOPARRelied on71402965USPTO
MOPARRelied on71414590USPTO
MOPARRelied on71424993USPTO
MOPARRelied on71430486USPTO
MOPARRelied on71430487USPTO
MOPARRelied on71430488USPTO
MOPARRelied on71430489USPTO
MOPARRelied on71430490USPTO
MOPARRelied on71430491USPTO
MOPARRelied on71572722USPTO

+11 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_8af8043d-4f95-40a7-9186-1340f999a841
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8af8043d-4f95-40a7-9186-1340f999a841",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91242458",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-07-17",
  "parties": [
    {
      "name": "FCA US LLC",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Gudsen Intelligent Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}