Opposition · USPTO

Opposition 91284891

OtherUSPTO

Opposition 91284891 at USPTO between Trek Bicycle Corporation and Merchants and Tradesmen, over the mark HOUNDTREK, filed May 9, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
May 9, 2023
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Respondent

Merchants and Tradesmen

Timeline

How the case has moved

Dates from the USPTO record and the HOUNDTREK filing.

  1. HOUNDTREK filed

    Application 97060110 filed at the USPTO.
  2. Opposition filed

    Trek Bicycle Corporation started opposition 91284891 at USPTO against HOUNDTREK.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
HOUNDTREKContested97060110USPTO
TREKRelied on73259070USPTO
TREK 100Relied on74580965USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
TREKRelied on75414082USPTO
ETREKRelied on75933601USPTO
TREK TRAVELRelied on76599435USPTO
TREK BICYCLE STORERelied on77221529USPTO
TREK 100Relied on77388493USPTO
TREKRelied on77388536USPTO
TREKRelied on77433264USPTO

+38 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_1d17c0fe-501d-4fac-b780-727fb3e6f146
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1d17c0fe-501d-4fac-b780-727fb3e6f146",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91284891",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-05-09",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "Merchants and Tradesmen",
      "role": "respondent"
    }
  ]
}