Opposition · USPTO

Opposition 91243687

OtherUSPTO

Opposition 91243687 at USPTO between Guess? IP Holder L.P. and Bachir Mombeleur, over the mark RIHCAB SUVAGE, filed Sep 19, 2018. Status in the office record: other.

View RIHCAB SUVAGEGet this data via the API
Status
Other
Result
Other
Filed
Sep 19, 2018
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Guess? IP Holder L.P.

Company trademarks
Respondent

Bachir Mombeleur

Timeline

How the case has moved

Dates from the USPTO record and the RIHCAB SUVAGE filing.

  1. RIHCAB SUVAGE filed

    Application 87856281 filed at the USPTO.

  2. Opposition filed

    Guess? IP Holder L.P. started opposition 91243687 at USPTO against RIHCAB SUVAGE.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
RIHCAB SUVAGEContested87856281USPTO
GUESS ?Relied on73369608USPTO
?Relied on74384739USPTO
[Design mark]Relied on75009861USPTO
[Design mark]Relied on75418506USPTO
[Design mark]Relied on75434561USPTO
[Design mark]Relied on75788249USPTO
?Relied on77290845USPTO
[Design mark]Relied on85627442USPTO
[Design mark]Relied on85984276USPTO
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_9aafe075-a0d6-4995-9f88-d2496aa92798
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9aafe075-a0d6-4995-9f88-d2496aa92798",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91243687",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-09-19",
  "parties": [
    {
      "name": "Guess? IP Holder L.P.",
      "role": "opponent"
    },
    {
      "name": "Bachir Mombeleur",
      "role": "respondent"
    }
  ]
}