Opposition · USPTO

Opposition 91201434

OtherUSPTO

Opposition 91201434 at USPTO between Newegg Inc. and Sopares Inc., over the mark THE EGG, filed Aug 31, 2011. Status in the office record: other.

View THE EGGGet this data via the API
Status
Other
Result
Other
Filed
Aug 31, 2011
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Newegg Inc.

Respondent

Sopares Inc.

Timeline

How the case has moved

Dates from the USPTO record and the THE EGG filing.

  1. THE EGG filed

    Application 77188510 filed at the USPTO.

  2. Opposition filed

    Newegg Inc. started opposition 91201434 at USPTO against THE EGG.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
THE EGGContested77188510USPTO
NEWEGG.COMRelied on76194750USPTO
NEWEGG MALLRelied on77124920USPTO
NEWEGGMALLRelied on77320505USPTO
EGGXPERTRelied on77404699USPTO
NEWEGGRelied on77404704USPTO
SHELL SHOCKERRelied on77517433USPTO
NEWEGG BUSINESSRelied on77706177USPTO
NEWEGGLOGISTICSRelied on77797545USPTO
NEWEGGRelied on77969138USPTO
NEWEGG.COMRelied on77969141USPTO
NEWEGGRelied on78915823USPTO

+1 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_1cbdd3b1-d2bd-4872-8323-bb04cb624261
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1cbdd3b1-d2bd-4872-8323-bb04cb624261",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91201434",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-08-31",
  "parties": [
    {
      "name": "Newegg Inc.",
      "role": "opponent"
    },
    {
      "name": "Sopares Inc.",
      "role": "respondent"
    }
  ]
}