Opposition · USPTO

Opposition 91248172

OtherUSPTO

Opposition 91248172 at USPTO between PopSockets LLC and Paul Erlandsen Strange, over the mark POPSICASE, filed May 8, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
May 8, 2019
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

PopSockets LLC

Company trademarks
Respondent

Paul Erlandsen Strange

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the POPSICASE filing.

  1. POPSICASE filed

    Application 79229999 filed at the USPTO.
  2. Opposition filed

    PopSockets LLC started opposition 91248172 at USPTO against POPSICASE.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
POPSICASEContested79229999USPTO
POPSOCKETSRelied on86149688USPTO
POPSOCKETSRelied on86149756USPTO
POPCLIPRelied on86560898USPTO
POPSOCKETSRelied on87198127USPTO
POPSOCKETSRelied on87674518USPTO
POPRelied on87726998USPTO
POP FOR PURPOSERelied on87856742USPTO
POPSOCKETSRelied on87924177USPTO
POPTIVISMRelied on88000525USPTO
POPRelied on88152124USPTO
POPRelied on88152128USPTO

+6 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 /v1/proceedings/{id}
ID=prc_5c29975d-a19b-4071-8ce0-68792a284f66
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5c29975d-a19b-4071-8ce0-68792a284f66",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91248172",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-05-08",
  "parties": [
    {
      "name": "PopSockets LLC",
      "role": "opponent"
    },
    {
      "name": "Paul Erlandsen Strange",
      "role": "respondent"
    }
  ]
}