Opposition · USPTO

Opposition 91300389

OtherUSPTO

Opposition 91300389 at USPTO between Razor USA LLC and Guangzhou Xianfeng Baiying E-commerce Co., Ltd., over the mark ERAZER, filed Jul 17, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 17, 2025
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Razor USA LLC

Company trademarks
Respondent

Guangzhou Xianfeng Baiying E-commerce Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the ERAZER filing.

  1. ERAZER filed

    Application 98706557 filed at the USPTO.
  2. Opposition filed

    Razor USA LLC started opposition 91300389 at USPTO against ERAZER.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
ERAZERContested98706557USPTO
RAZORRelied on75555257USPTO
RAZORRelied on75909096USPTO
RAZORRelied on76066012USPTO
RAZORRelied on76066017USPTO
RAZRRelied on78750797USPTO
RAZRRelied on78750841USPTO
RAZORRelied on85031199USPTO
AUTHENTIC BLACK LABEL RAZORRelied on85038277USPTO
RAZRRelied on88253841USPTO
RAZORRelied on88658391USPTO
RAZORRelied on88978404USPTO
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_65cc976d-1652-4a69-b2a9-b4bbf460bd4d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_65cc976d-1652-4a69-b2a9-b4bbf460bd4d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300389",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-07-17",
  "parties": [
    {
      "name": "Razor USA LLC",
      "role": "opponent"
    },
    {
      "name": "Guangzhou Xianfeng Baiying E-commerce Co., Ltd.",
      "role": "respondent"
    }
  ]
}