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.
Respondent
Shenzhen Reach Interactive Technologies Ltd
Timeline
How the case has moved
Dates from the USPTO record and the AURATREK filing.
AURATREK filed
Application 98633899 filed at the USPTO.Opposition filed
Trek Bicycle Corporation started opposition 91297215 at USPTO against AURATREK.
Marks
Marks involved
1 contested mark, 10 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| AURATREK | Contested | 98633899 | USPTO |
| TREK | Relied on | 73259070 | USPTO |
| TREK | Relied on | 74583173 | USPTO |
| TREKKING | Relied on | 74604152 | USPTO |
| TREK | Relied on | 77388536 | USPTO |
| TREK | Relied on | 78171262 | USPTO |
| TREK | Relied on | 78316205 | USPTO |
| TREK | Relied on | 85065052 | USPTO |
| TREK | Relied on | 85085438 | USPTO |
| TREK | Relied on | 86743992 | USPTO |
| TREK LIGHT GEAR | Relied on | 90718119 | USPTO |
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_33b74872-f68b-4690-b0ab-f191bc2a72dd
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_33b74872-f68b-4690-b0ab-f191bc2a72dd",
"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"
}
]
}