Opposition · USPTO

Opposition 91264274

OtherUSPTO

Opposition 91264274 at USPTO between Ryder System, Inc. and Rydr Technologies, Inc, over the mark RYDR, filed Aug 18, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 18, 2020
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Ryder System, Inc.

Company trademarks
Respondent

Rydr Technologies, Inc

Timeline

How the case has moved

Dates from the USPTO record and the RYDR filing.

  1. RYDR filed

    Application 88416984 filed at the USPTO.
  2. Opposition filed

    Ryder System, Inc. started opposition 91264274 at USPTO against RYDR.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
RYDRContested88416984USPTO
RYDERRelied on73174200USPTO
RYDER SYSTEMRelied on73677484USPTO
RYDERRelied on73796158USPTO
RYDERRelied on75001854USPTO
1-800-GO-RYDERRelied on75037440USPTO
RYDERRelied on75104965USPTO
RYDER TRANSPORTATION SERVICESRelied on75117690USPTO
RYDERSHIPRelied on75923108USPTO
RYDERTRACRelied on76150638USPTO
RYDERFLOWRelied on76150639USPTO
RYDERENTRYRelied on76242806USPTO

+8 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_11209891-91c6-4373-96bd-3997bae83e0a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_11209891-91c6-4373-96bd-3997bae83e0a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91264274",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-08-18",
  "parties": [
    {
      "name": "Ryder System, Inc.",
      "role": "opponent"
    },
    {
      "name": "Rydr Technologies, Inc",
      "role": "respondent"
    }
  ]
}