Opposition · USPTO

Opposition 91211241

OtherUSPTO

Opposition 91211241 at USPTO between Sterling Mets, L.P. and Condemned Few, LLC, over the mark CONDEMNED FEW MC NEW YORK, filed Jun 12, 2013. Status in the office record: other.

View CONDEMNED FEW MC NEW YORKGet this data via the API
Status
Other
Result
Other
Filed
Jun 12, 2013
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Sterling Mets, L.P.

Company trademarks
Respondent

Condemned Few, LLC

Timeline

How the case has moved

Dates from the USPTO record and the CONDEMNED FEW MC NEW YORK filing.

  1. CONDEMNED FEW MC NEW YORK filed

    Application 85663373 filed at the USPTO.

  2. Opposition filed

    Sterling Mets, L.P. started opposition 91211241 at USPTO against CONDEMNED FEW MC NEW YORK.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
CONDEMNED FEW MC NEW YORKContested85663373USPTO
NYRelied on73283759USPTO
NEW YORK METSRelied on73677145USPTO
NYRelied on73744369USPTO
NYRelied on76169458USPTO
NYRelied on78737337USPTO
NYRelied on78737366USPTO
NYRelied on78737368USPTO
NEW YORKRelied on85099861USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_49406451-bdeb-4330-90bc-20e6e5821526
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_49406451-bdeb-4330-90bc-20e6e5821526",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91211241",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-06-12",
  "parties": [
    {
      "name": "Sterling Mets, L.P.",
      "role": "opponent"
    },
    {
      "name": "Condemned Few, LLC",
      "role": "respondent"
    }
  ]
}