Opposition · USPTO

Opposition 91283831

OtherUSPTO

Opposition 91283831 at USPTO between Nova Bus Inc. and Zhejiang Cfmoto Power Co., Ltd., over the mark PAPIO NOVA, filed Mar 8, 2023. Status in the office record: other.

View PAPIO NOVAGet this data via the API
Status
Other
Result
Other
Filed
Mar 8, 2023
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Nova Bus Inc.

Company trademarks
Respondent

Zhejiang Cfmoto Power Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the PAPIO NOVA filing.

  1. PAPIO NOVA filed

    Application 97318599 filed at the USPTO.

  2. Opposition filed

    Nova Bus Inc. started opposition 91283831 at USPTO against PAPIO NOVA.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
PAPIO NOVAContested97318599USPTO
NOVA BUSRelied on76343482USPTO
NOVA BUSRelied on76343486USPTO
NOVABUSRelied on76479340USPTO
NOVA LFSRelied on76484149USPTO
NOVABUSRelied on77833811USPTO
NOVABUSRelied on77833840USPTO
NOVABUSRelied on77833859USPTO
NOVABUSRelied on78198529USPTO
NOVA LFSRelied on78205766USPTO
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_7cdc751e-8421-49c7-be59-72dddd216426
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7cdc751e-8421-49c7-be59-72dddd216426",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283831",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-03-08",
  "parties": [
    {
      "name": "Nova Bus Inc.",
      "role": "opponent"
    },
    {
      "name": "ZHEJIANG CFMOTO POWER CO., LTD.",
      "role": "respondent"
    }
  ]
}