Opposition · USPTO

Opposition 91255598

OtherUSPTO

Opposition 91255598 at USPTO between Chicago Cubs Baseball Club, LLC and Cubi Inc., over the mark CUBI, filed May 1, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
May 1, 2020
Marks involved
33
Parties

Who is involved

The parties as named in the office record.

Opponent

Chicago Cubs Baseball Club, LLC

Respondent

Cubi Inc.

Timeline

How the case has moved

Dates from the USPTO record and the CUBI filing.

  1. CUBI filed

    Application 88257489 filed at the USPTO.
  2. Opposition filed

    Chicago Cubs Baseball Club, LLC started opposition 91255598 at USPTO against CUBI.
Marks

Marks involved

1 contested mark, 32 marks the challenger relies on.

MarkRoleApplicationOffice
CUBIContested88257489USPTO
CUBSRelied on72278467USPTO
CUBSRelied on73011582USPTO
[Design mark]Relied on73752274USPTO
WRIGLEY FIELD HOME OF CHICAGO CUBSRelied on73752544USPTO
CHICAGO CUBSRelied on73752741USPTO
CHICAGO CUBSRelied on73752742USPTO
CUBSRelied on73753285USPTO
CHICAGO CUBSRelied on73762765USPTO
CHICAGO CUBSRelied on73762807USPTO
CUBS CARERelied on74173748USPTO
MR. CUBRelied on74446388USPTO

+21 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_7d7f714d-7f26-443a-a70a-180749a937b1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7d7f714d-7f26-443a-a70a-180749a937b1",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91255598",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-05-01",
  "parties": [
    {
      "name": "Chicago Cubs Baseball Club, LLC",
      "role": "opponent"
    },
    {
      "name": "Cubi Inc.",
      "role": "respondent"
    }
  ]
}