Opposition · USPTO

Opposition 91216149

OtherUSPTO

Opposition 91216149 at USPTO between Trek Bicycle Corporation and Semsons, over the mark I.TREK, filed May 27, 2015. Status in the office record: other.

View I.TREKGet this data via the API
Status
Other
Result
Other
Filed
May 27, 2015
Marks involved
29
Parties

Who is involved

The parties as named in the office record.

Opponent

Trek Bicycle Corporation

Respondent

Semsons

Timeline

How the case has moved

Dates from the USPTO record and the I.TREK filing.

  1. I.TREK filed

    Application 86089716 filed at the USPTO.

  2. Opposition filed

    Trek Bicycle Corporation started opposition 91216149 at USPTO against I.TREK.
Marks

Marks involved

1 contested mark, 28 marks the challenger relies on.

MarkRoleApplicationOffice
I.TREKContested86089716USPTO
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

+17 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_6fb69d2b-d710-4a50-9b10-edf26c0bd2f7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6fb69d2b-d710-4a50-9b10-edf26c0bd2f7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91216149",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-05-27",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "opponent"
    },
    {
      "name": "Semsons",
      "role": "respondent"
    }
  ]
}