Opposition · USPTO

Opposition 91305363

OtherUSPTO

Opposition 91305363 at USPTO between Trek Bicycle Corporation and Etrek LLC, over the mark ETREK, filed Feb 19, 2026. Status in the office record: other.

View ETREKGet this data via the API
Status
Other
Result
Other
Filed
Feb 19, 2026
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Company trademarks
Respondent

Etrek LLC

Timeline

How the case has moved

Dates from the USPTO record and the ETREK filing.

  1. ETREK filed

    Application 99298373 filed at the USPTO.

  2. Opposition filed

    Trek Bicycle Corporation started opposition 91305363 at USPTO against ETREK.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
ETREKContested99298373USPTO
TREKRelied on73259070USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
ETREKRelied on75933601USPTO
TREK TRAVELRelied on76599435USPTO
TREKRelied on78171262USPTO
TREKERRelied on78182435USPTO
TREK UNIVERSITYRelied on78447581USPTO
TREKRelied on85065052USPTO
TREKRelied on85085438USPTO
TREKRelied on85085570USPTO

+5 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_805964a8-a5c8-4cf8-b78c-1c5b832aca0b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_805964a8-a5c8-4cf8-b78c-1c5b832aca0b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91305363",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-02-19",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "ETREK LLC",
      "role": "respondent"
    }
  ]
}