Opposition · USPTO

Opposition 91273107

OtherUSPTO

Opposition 91273107 at USPTO between Epic Games, Inc. and Platini Love Epic, over the mark DR. EPIC, filed Nov 24, 2021. Status in the office record: other.

View DR. EPICGet this data via the API
Status
Other
Result
Other
Filed
Nov 24, 2021
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Epic Games, Inc.

Company trademarks
Respondent

Platini Love Epic

Timeline

How the case has moved

Dates from the USPTO record and the DR. EPIC filing.

  1. DR. EPIC filed

    Application 90370272 filed at the USPTO.

  2. Opposition filed

    Epic Games, Inc. started opposition 91273107 at USPTO against DR. EPIC.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
DR. EPICContested90370272USPTO
EPIC GAMESRelied on75133405USPTO
EPICRelied on75134488USPTO
EPIC PINBALLRelied on85371386USPTO
EPIC GAMESRelied on87842174USPTO
EPIC GAMESRelied on87842183USPTO
EPIC GAMESRelied on88210615USPTO
EPIC GAMES STORERelied on88258782USPTO
EPIC GAMES STORERelied on88258787USPTO
EPIC GAMESRelied on88872693USPTO
EPICRelied on88872699USPTO
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_0f76f6ab-f9a6-47ff-9571-3700a761ab80
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0f76f6ab-f9a6-47ff-9571-3700a761ab80",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91273107",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-11-24",
  "parties": [
    {
      "name": "Epic Games, Inc.",
      "role": "opponent"
    },
    {
      "name": "Platini Love Epic",
      "role": "respondent"
    }
  ]
}