Opposition · USPTO

Opposition 91294034

OtherUSPTO

Opposition 91294034 at USPTO between Fca Us LLC and Hangzhou Qisheng Electronic Commerce Co., Ltd., over the mark MOCAR7, filed Sep 17, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 17, 2024
Marks involved
23
Parties

Who is involved

The parties as named in the office record.

Opponent

Fca Us LLC

Company trademarks
Respondent

Hangzhou Qisheng Electronic Commerce Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the MOCAR7 filing.

  1. MOCAR7 filed

    Application 98123076 filed at the USPTO.
  2. Opposition filed

    Fca Us LLC started opposition 91294034 at USPTO against MOCAR7.
Marks

Marks involved

1 contested mark, 22 marks the challenger relies on.

MarkRoleApplicationOffice
MOCAR7Contested98123076USPTO
MOPARRelied on71402965USPTO
MOPARRelied on71414590USPTO
MOPARRelied on71424993USPTO
MOPARRelied on71430486USPTO
MOPARRelied on71430487USPTO
MOPARRelied on71430488USPTO
MOPARRelied on71430489USPTO
MOPARRelied on71430490USPTO
MOPARRelied on71430491USPTO
MOPARRelied on71572722USPTO
MOPAR SPEEDSHOPRelied on78206808USPTO

+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_44bb7351-058c-4b09-9554-32ae4e0cdec4
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_44bb7351-058c-4b09-9554-32ae4e0cdec4",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91294034",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-09-17",
  "parties": [
    {
      "name": "FCA US LLC",
      "role": "opponent"
    },
    {
      "name": "Hangzhou Qisheng Electronic Commerce Co., Ltd.",
      "role": "respondent"
    }
  ]
}