Opposition · USPTO

Opposition 91297215

OtherUSPTO

Opposition 91297215 at USPTO between Trek Bicycle Corporation and Shenzhen Reach Interactive Technologies Ltd, over the mark AURATREK, filed Feb 25, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 25, 2025
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Company trademarks
Respondent

Shenzhen Reach Interactive Technologies Ltd

Timeline

How the case has moved

Dates from the USPTO record and the AURATREK filing.

  1. AURATREK filed

    Application 98633899 filed at the USPTO.
  2. Opposition filed

    Trek Bicycle Corporation started opposition 91297215 at USPTO against AURATREK.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
AURATREKContested98633899USPTO
TREKRelied on73259070USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
TREKRelied on77388536USPTO
TREKRelied on78171262USPTO
TREKRelied on78316205USPTO
TREKRelied on85065052USPTO
TREKRelied on85085438USPTO
TREKRelied on86743992USPTO
TREK LIGHT GEARRelied on90718119USPTO
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_742291ae-f244-4227-b647-1f8d715eb42a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_742291ae-f244-4227-b647-1f8d715eb42a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91297215",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-02-25",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Reach Interactive Technologies Ltd",
      "role": "respondent"
    }
  ]
}