Opposition · USPTO

Opposition 91241749

OtherUSPTO

Opposition 91241749 at USPTO between Marvel Characters, Inc. and Li Guoqiang, over the mark MARVEL O BUG, filed Jun 12, 2018. Status in the office record: other.

View MARVEL O BUGGet this data via the API
Status
Other
Result
Other
Filed
Jun 12, 2018
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Marvel Characters, Inc.

Company trademarks
Respondent

Li Guoqiang

Timeline

How the case has moved

Dates from the USPTO record and the MARVEL O BUG filing.

  1. MARVEL O BUG filed

    Application 87170377 filed at the USPTO.

  2. Opposition filed

    Marvel Characters, Inc. started opposition 91241749 at USPTO against MARVEL O BUG.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
MARVEL O BUGContested87170377USPTO
MARVELRelied on74214398USPTO
MARVEL COMICS MRelied on74214617USPTO
THE MARVEL ALTERNIVERSE STORERelied on75171115USPTO
MARVELRelied on78536382USPTO
MARVELRelied on85319117USPTO
MARVELRelied on85319119USPTO
MARVELRelied on85319130USPTO
MARVELRelied on85319232USPTO
CAPTAIN MARVELRelied on86435556USPTO
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_31e01056-1fcc-4358-8a17-3761b927fcf0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_31e01056-1fcc-4358-8a17-3761b927fcf0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91241749",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-06-12",
  "parties": [
    {
      "name": "Marvel Characters, Inc.",
      "role": "opponent"
    },
    {
      "name": "Li Guoqiang",
      "role": "respondent"
    }
  ]
}