Opposition · USPTO

Opposition 91199351

OtherUSPTO

Opposition 91199351 at USPTO between LCS International B.V. and Runner's Roost, LLC, over the mark [Design Mark], filed Apr 8, 2011. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 8, 2011
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

LCS International B.V.

Respondent

Runner's Roost, LLC

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 77877922 filed at the USPTO.
  2. Opposition filed

    LCS International B.V. started opposition 91199351 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested77877922USPTO
LE COQ SPORTIFRelied on73142879USPTO
LE COQ SPORTIFRelied on73142880USPTO
LE COQ SPORTIFRelied on73142882USPTO
[Design mark]Relied on73245263USPTO
[Design mark]Relied on73245264USPTO
[Design mark]Relied on73245266USPTO
LE COQ SPORTIFRelied on73245294USPTO
LE COQ SPORTIFRelied on73245296USPTO
LE COQ SPORTIFRelied on73245297USPTO
LE COQ SPORTIFRelied on79077574USPTO
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_41b5b9f4-1de2-48be-8baf-f59e3b9b750f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_41b5b9f4-1de2-48be-8baf-f59e3b9b750f",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91199351",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-04-08",
  "parties": [
    {
      "name": "LCS International B.V.",
      "role": "opponent"
    },
    {
      "name": "Runner's Roost, LLC",
      "role": "respondent"
    }
  ]
}