Opposition · USPTO

Opposition 91216916

OtherUSPTO

Opposition 91216916 at USPTO between Trek Bicycle Corporation and FTR Systems, Inc., over the mark FTR CADDYTREK, filed Jun 18, 2014. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 18, 2014
Marks involved
30
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Respondent

FTR Systems, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the FTR CADDYTREK filing.

  1. FTR CADDYTREK filed

    Application 86137462 filed at the USPTO.
  2. Opposition filed

    Trek Bicycle Corporation started opposition 91216916 at USPTO against FTR CADDYTREK.
Marks

Marks involved

1 contested mark, 29 marks the challenger relies on.

MarkRoleApplicationOffice
FTR CADDYTREKContested86137462USPTO
TREKRelied on73259070USPTO
TREK 100Relied on74580965USPTO
TREKRelied on74583173USPTO
TREKKINGRelied on74604152USPTO
TREKRelied on75349577USPTO
TREKRelied on75414082USPTO
ETREKRelied on75933601USPTO
TREK TRAVELRelied on76599435USPTO
TREK BICYCLE STORERelied on77221529USPTO
TREK 100Relied on77388493USPTO
TREKRelied on77388536USPTO

+18 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_f6f3b934-73f8-4ee0-9d51-ca83973be392
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f6f3b934-73f8-4ee0-9d51-ca83973be392",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91216916",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-06-18",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "FTR Systems, Inc.",
      "role": "respondent"
    }
  ]
}