Opposition · USPTO

Opposition 91302144

OtherUSPTO

Opposition 91302144 at USPTO between The Carnegie Hall Corporation and Carnegie Hospitality, LLC, over the mark CARNEGIE DINER & CAFE, filed Oct 2, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 2, 2025
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

The Carnegie Hall Corporation

Respondent

Carnegie Hospitality, LLC

Timeline

How the case has moved

Dates from the USPTO record and the CARNEGIE DINER & CAFE filing.

  1. CARNEGIE DINER & CAFE filed

    Application 99040389 filed at the USPTO.
  2. Opposition filed

    The Carnegie Hall Corporation started opposition 91302144 at USPTO against CARNEGIE DINER & CAFE.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
CARNEGIE DINER & CAFEContested99040389USPTO
CARNEGIE HALLRelied on73783920USPTO
CARNEGIE HALLRelied on74065273USPTO
CARNEGIE HALLRelied on75426593USPTO
CARNEGIE HALL LISTENING ADVENTURESRelied on76975103USPTO
LIVE AT CARNEGIE HALLRelied on78727796USPTO
CARNEGIE HALLRelied on88639608USPTO
CARNEGIE HALL+Relied on97157167USPTO
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_1585969c-03c8-44d2-8bc6-69ccc41d5f4a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1585969c-03c8-44d2-8bc6-69ccc41d5f4a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302144",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-10-02",
  "parties": [
    {
      "name": "The Carnegie Hall Corporation",
      "role": "opponent"
    },
    {
      "name": "Carnegie Hospitality, LLC",
      "role": "respondent"
    }
  ]
}