Opposition · USPTO

Opposition 91308210

OtherUSPTO

Opposition 91308210 at USPTO between Hypebeast Hong Kong Limited and James Nash Seawell, over the mark HYPEBEAST HIPPIE, filed Jun 18, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 18, 2026
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Hypebeast Hong Kong Limited

Company trademarks
Respondent

James Nash Seawell

Timeline

How the case has moved

Dates from the USPTO record and the HYPEBEAST HIPPIE filing.

  1. HYPEBEAST HIPPIE filed

    Application 99496499 filed at the USPTO.
  2. Opposition filed

    Hypebeast Hong Kong Limited started opposition 91308210 at USPTO against HYPEBEAST HIPPIE.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
HYPEBEAST HIPPIEContested99496499USPTO
HYPEBEASTRelied on77414063USPTO
HYPEBEASTRelied on87242827USPTO
HYPEBEASTRelied on87242833USPTO
HYPEBEAST RADIORelied on88006805USPTO
HYPEBEASTRelied on90880139USPTO
HYPEBEASTRelied on90880172USPTO
HYPEBEASTRelied on90880256USPTO
HYPEBEASTRelied on90880294USPTO
HYPEBEAST GOODS AND SERVICESRelied on97746224USPTO
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_e290b7b4-218d-4bd0-ad03-1b4348269930
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e290b7b4-218d-4bd0-ad03-1b4348269930",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91308210",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-06-18",
  "parties": [
    {
      "name": "Hypebeast Hong Kong Limited",
      "role": "opponent"
    },
    {
      "name": "James Nash Seawell",
      "role": "respondent"
    }
  ]
}