Opposition · USPTO

Opposition 91277779

OtherUSPTO

Opposition 91277779 at USPTO between Trek Bicycle Corporation and RightOnTrek, Inc., over the mark RIGHTONTREK, filed Aug 5, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 5, 2022
Marks involved
49
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Respondent

RightOnTrek, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the RIGHTONTREK filing.

  1. RIGHTONTREK filed

    Application 90527749 filed at the USPTO.
  2. Opposition filed

    Trek Bicycle Corporation started opposition 91277779 at USPTO against RIGHTONTREK.
Marks

Marks involved

2 contested marks, 47 marks the challenger relies on.

MarkRoleApplicationOffice
RIGHTONTREKContested90527749USPTO
RIGHTONTREKContested90527753USPTO
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

+37 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_317579ee-1cc8-4927-b6a8-b5f0cefeac7b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_317579ee-1cc8-4927-b6a8-b5f0cefeac7b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91277779",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-08-05",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "RightOnTrek, Inc.",
      "role": "respondent"
    }
  ]
}