Opposition · USPTO

Opposition 91303741

OtherUSPTO

Opposition 91303741 at USPTO between Wahl Clipper Corporation and Nicebay Holdings Inc, over the mark WHALLPRO, filed Dec 13, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 13, 2025
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Wahl Clipper Corporation

Company trademarks
Respondent

Nicebay Holdings Inc

Timeline

How the case has moved

Dates from the USPTO record and the WHALLPRO filing.

  1. WHALLPRO filed

    Application 99048001 filed at the USPTO.
  2. Opposition filed

    Wahl Clipper Corporation started opposition 91303741 at USPTO against WHALLPRO.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
WHALLPROContested99048001USPTO
WAHLRelied on71573018USPTO
WAHLRelied on71594161USPTO
WAHLRelied on72047479USPTO
WAHLRelied on73136220USPTO
WAHLRelied on73518739USPTO
WAHLRelied on74082971USPTO
WAHL LITHIUM IONRelied on85976458USPTO
WAHL PRO IONRelied on86071861USPTO
WAHL PROFESSIONALRelied on87657321USPTO
WAHLRelied on87923912USPTO
WAHLRelied on90373003USPTO

+4 more marks in this case

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_909ecc0c-4abf-41b8-a8f2-a2e6a79a0bae
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_909ecc0c-4abf-41b8-a8f2-a2e6a79a0bae",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91303741",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-12-13",
  "parties": [
    {
      "name": "Wahl Clipper Corporation",
      "role": "opponent"
    },
    {
      "name": "Nicebay Holdings Inc",
      "role": "respondent"
    }
  ]
}