Opposition · USPTO

Opposition 91213954

OtherUSPTO

Opposition 91213954 at USPTO between Apple Inc. and Mark Stein, over the mark IBROKEN, filed Dec 11, 2013. Status in the office record: other.

View IBROKENGet this data via the API
Status
Other
Result
Other
Filed
Dec 11, 2013
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Mark Stein

Timeline

How the case has moved

Dates from the USPTO record and the IBROKEN filing.

  1. IBROKEN filed

    Application 85684154 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91213954 at USPTO against IBROKEN.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
IBROKENContested85684154USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
[Design mark]Relied on76426501USPTO
[Design mark]Relied on76432531USPTO
APPLERelied on77172511USPTO
IPHONERelied on77353055USPTO
APPLE STORERelied on77388365USPTO
APPLECARERelied on77499797USPTO
APPLECARERelied on77499829USPTO
APPLECARERelied on77499847USPTO
[Design mark]Relied on77648705USPTO

+3 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_17af6565-09da-4b43-b809-69d6a34188a0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_17af6565-09da-4b43-b809-69d6a34188a0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91213954",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-12-11",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Mark Stein",
      "role": "respondent"
    }
  ]
}