Opposition 91299847
OtherUSPTO
Opposition 91299847 at USPTO between Trek Bicycle Corporation and Grace A. Yamada, over the mark RIGTREK, filed Jun 20, 2025. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jun 20, 2025
- Marks involved
- 24
Parties
Who is involved
The parties as named in the office record.
Respondent
Grace A. Yamada
Timeline
How the case has moved
Dates from the USPTO record and the RIGTREK filing.
RIGTREK filed
Application 98791470 filed at the USPTO.Opposition filed
Trek Bicycle Corporation started opposition 91299847 at USPTO against RIGTREK.
Marks
Marks involved
1 contested mark, 23 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| RIGTREK | Contested | 98791470 | USPTO |
| TREK | Relied on | 73259070 | USPTO |
| TREK | Relied on | 74583173 | USPTO |
| TREKKING | Relied on | 74604152 | USPTO |
| TREK | Relied on | 75414082 | USPTO |
| TREK BICYCLE STORE | Relied on | 77221529 | USPTO |
| TREK | Relied on | 77937970 | USPTO |
| TREKLITE | Relied on | 78085960 | USPTO |
| TREK | Relied on | 78171262 | USPTO |
| TREKMATES | Relied on | 79088328 | USPTO |
| DUAL TREKKER | Relied on | 79164060 | USPTO |
| TREK | Relied on | 85065052 | USPTO |
+12 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_2d129972-f2bb-41c6-9080-e423bfcdc125
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_2d129972-f2bb-41c6-9080-e423bfcdc125",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91299847",
"status": "other",
"office_code": "US",
"filed_date": "2025-06-20",
"parties": [
{
"name": "Trek Bicycle Corporation",
"role": "opponent"
},
{
"name": "Grace A. Yamada",
"role": "respondent"
}
]
}