Opposition · USPTO

Opposition 91251430

OtherUSPTO

Opposition 91251430 at USPTO between Chicago Cubs Baseball Club, LLC and Covered Cubs, LLC, over the mark COVERED CUBS, filed Oct 7, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 7, 2019
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Chicago Cubs Baseball Club, LLC

Respondent

Covered Cubs, LLC

Timeline

How the case has moved

Dates from the USPTO record and the COVERED CUBS filing.

  1. COVERED CUBS filed

    Application 87892481 filed at the USPTO.
  2. Opposition filed

    Chicago Cubs Baseball Club, LLC started opposition 91251430 at USPTO against COVERED CUBS.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
COVERED CUBSContested87892481USPTO
CUBSRelied on72278467USPTO
CUBSRelied on73011582USPTO
CHICAGO CUBSRelied on73762807USPTO
CUBS CARERelied on74173748USPTO
MR. CUBRelied on74446388USPTO
CUBSRelied on77609507USPTO
CUBSRelied on78633651USPTO
CUBSRelied on78633652USPTO
CUBSRelied on78633653USPTO
CUBSRelied on78633654USPTO
CUBSRelied on78633655USPTO

+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_82b3ddc8-f363-46ba-9d65-cba59154cbe0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_82b3ddc8-f363-46ba-9d65-cba59154cbe0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91251430",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-10-07",
  "parties": [
    {
      "name": "Chicago Cubs Baseball Club, LLC",
      "role": "opponent"
    },
    {
      "name": "Covered Cubs, LLC",
      "role": "respondent"
    }
  ]
}