Opposition · USPTO

Opposition 91306755

OtherUSPTO

Opposition 91306755 at USPTO between The Cincinnati Reds LLC and Zhuzhou Yinfeng Technology Co., Ltd., over the mark REDSONE, filed Apr 21, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 21, 2026
Marks involved
36
Parties

Who is involved

The parties as named in the office record.

Opponent

The Cincinnati Reds LLC

Respondent

Zhuzhou Yinfeng Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the REDSONE filing.

  1. REDSONE filed

    Application 99261270 filed at the USPTO.
  2. Opposition filed

    The Cincinnati Reds LLC started opposition 91306755 at USPTO against REDSONE.
Marks

Marks involved

1 contested mark, 35 marks the challenger relies on.

MarkRoleApplicationOffice
REDSONEContested99261270USPTO
CINCINNATI REDSRelied on72319280USPTO
REDSRelied on73177983USPTO
REDSRelied on73178051USPTO
REDSRelied on73178052USPTO
REDSRelied on73178054USPTO
REDSRelied on73178206USPTO
REDSRelied on73178207USPTO
REDSRelied on73178298USPTO
REDSRelied on73178299USPTO
REDSRelied on73178304USPTO
REDSRelied on73178307USPTO

+24 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_4348dcf7-47b6-4ba8-9263-ce62e7458818
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4348dcf7-47b6-4ba8-9263-ce62e7458818",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306755",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-04-21",
  "parties": [
    {
      "name": "The Cincinnati Reds LLC",
      "role": "opponent"
    },
    {
      "name": "Zhuzhou Yinfeng Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}