Opposition · USPTO

Opposition 91300342

OtherUSPTO

Opposition 91300342 at USPTO between Trek Bicycle Corporation and Momentum Mavens Inc, over the mark TREKO, filed Jul 11, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 11, 2025
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Company trademarks
Respondent

Momentum Mavens Inc

Timeline

How the case has moved

Dates from the USPTO record and the TREKO filing.

  1. TREKO filed

    Application 98900404 filed at the USPTO.
  2. Opposition filed

    Trek Bicycle Corporation started opposition 91300342 at USPTO against TREKO.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
TREKOContested98900404USPTO
TREKRelied on73259070USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
ETREKRelied on75933601USPTO
TREK BICYCLE STORERelied on77221529USPTO
TREKRelied on77433264USPTO
TREKRelied on78171262USPTO
DUAL TREKKERRelied on79164060USPTO
TREKRelied on85065052USPTO
TREK BICYCLES OF TUCSONRelied on85173419USPTO
TREKRelied on86006347USPTO

+6 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_4e40e978-4d4d-4107-b7e0-481c93238478
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4e40e978-4d4d-4107-b7e0-481c93238478",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300342",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-07-11",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "Momentum Mavens Inc",
      "role": "respondent"
    }
  ]
}