Opposition · USPTO

Opposition 91291131

OtherUSPTO

Opposition 91291131 at USPTO between Trek Bicycle Corporation and Packet Digital LLC, over the mark POWERTREK, filed Apr 25, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 25, 2024
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Company trademarks
Respondent

Packet Digital LLC

Timeline

How the case has moved

Dates from the USPTO record and the POWERTREK filing.

  1. POWERTREK filed

    Application 98171717 filed at the USPTO.
  2. Opposition filed

    Trek Bicycle Corporation started opposition 91291131 at USPTO against POWERTREK.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
POWERTREKContested98171717USPTO
TREKRelied on73259070USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
ETREKRelied on75933601USPTO
TREK BICYCLE STORERelied on77221529USPTO
TREKRelied on77433264USPTO
TREKRelied on78171262USPTO
TREKRelied on85065052USPTO
TREKRelied on86743992USPTO
PRO TREK SMARTRelied on87048301USPTO
PRO TREKRelied on87048310USPTO

+3 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_fd8486ca-1da2-46af-80e2-5d8c6a9f7fb5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fd8486ca-1da2-46af-80e2-5d8c6a9f7fb5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91291131",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-04-25",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "Packet Digital LLC",
      "role": "respondent"
    }
  ]
}