Opposition · USPTO

Opposition 91300627

OtherUSPTO

Opposition 91300627 at USPTO between Epic Games, Inc. and Epic Swim Maui LLC, over the mark EPIC SWIM, filed Jul 25, 2025. Status in the office record: other.

View EPIC SWIMGet this data via the API
Status
Other
Result
Other
Filed
Jul 25, 2025
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Epic Games, Inc.

Company trademarks
Respondent

Epic Swim Maui LLC

Timeline

How the case has moved

Dates from the USPTO record and the EPIC SWIM filing.

  1. EPIC SWIM filed

    Application 98317176 filed at the USPTO.

  2. Opposition filed

    Epic Games, Inc. started opposition 91300627 at USPTO against EPIC SWIM.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
EPIC SWIMContested98317176USPTO
EPICRelied on75134488USPTO
EPIC GAMESRelied on87842174USPTO
EPIC GAMESRelied on87842183USPTO
EPIC GAMESRelied on88210615USPTO
EPIC GAMESRelied on88210623USPTO
EPIC GAMESRelied on88872693USPTO
EPICRelied on88872699USPTO
EPIC GAMES PUBLISHINGRelied on88985357USPTO
EPIC STUDIOSRelied on97052476USPTO
EPICLABSRelied on97851641USPTO
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_d49b53ae-e748-458d-84a4-8eeee47f6b38
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d49b53ae-e748-458d-84a4-8eeee47f6b38",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300627",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-07-25",
  "parties": [
    {
      "name": "Epic Games, Inc.",
      "role": "opponent"
    },
    {
      "name": "Epic Swim Maui LLC",
      "role": "respondent"
    }
  ]
}