Opposition · USPTO

Opposition 91297684

OtherUSPTO

Opposition 91297684 at USPTO between Trek Bicycle Corporation and Pingan Huo, over the mark YTREC, filed Mar 18, 2025. Status in the office record: other.

View YTRECGet this data via the API
Status
Other
Result
Other
Filed
Mar 18, 2025
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Respondent

Pingan Huo

Timeline

How the case has moved

Dates from the USPTO record and the YTREC filing.

  1. YTREC filed

    Application 98639706 filed at the USPTO.

  2. Opposition filed

    Trek Bicycle Corporation started opposition 91297684 at USPTO against YTREC.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
YTRECContested98639706USPTO
TREKRelied on73259070USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
ETREKRelied on75933601USPTO
TREK BICYCLE STORERelied on77221529USPTO
TREKRelied on77433264USPTO
TREKRelied on78171262USPTO
TREKRelied on85065052USPTO
TREKRelied on86743992USPTO
PRO TREK SMARTRelied on87048301USPTO
PRO TREKRelied on87048310USPTO

+5 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_443461f3-cca9-497f-bd18-22eb47e6edbf
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_443461f3-cca9-497f-bd18-22eb47e6edbf",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91297684",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-03-18",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "Pingan Huo",
      "role": "respondent"
    }
  ]
}