Opposition · USPTO

Opposition 91299833

OtherUSPTO

Opposition 91299833 at USPTO between A Place for Rover, Inc. and Yok Chong Chi, over the mark ROVER'S EDGE, filed Jun 18, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 18, 2025
Marks involved
23
Parties

Who is involved

The parties as named in the office record.

Opponent

A Place for Rover, Inc.

Company trademarks
Respondent

Yok Chong Chi

Timeline

How the case has moved

Dates from the USPTO record and the ROVER'S EDGE filing.

  1. ROVER'S EDGE filed

    Application 98847559 filed at the USPTO.
  2. Opposition filed

    A Place for Rover, Inc. started opposition 91299833 at USPTO against ROVER'S EDGE.
Marks

Marks involved

1 contested mark, 22 marks the challenger relies on.

MarkRoleApplicationOffice
ROVER'S EDGEContested98847559USPTO
ROVERRelied on85519439USPTO
ROVERRelied on86832450USPTO
ROVERRelied on86841189USPTO
ROVER.COM THE DOG PEOPLERelied on87500180USPTO
ROVERRelied on90671983USPTO
ROVERRelied on90671991USPTO
ROVERRelied on90671997USPTO
ROVERRelied on90672016USPTO
ROVERRelied on90976457USPTO
ROVERRelied on97259583USPTO
ROVERRelied on97259593USPTO

+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_582ed7cb-30cf-4b17-88d1-578bbb1cc787
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_582ed7cb-30cf-4b17-88d1-578bbb1cc787",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91299833",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-06-18",
  "parties": [
    {
      "name": "A Place for Rover, Inc.",
      "role": "opponent"
    },
    {
      "name": "Yok Chong Chi",
      "role": "respondent"
    }
  ]
}