Cancellation · USPTO

Cancellation 92085317

OtherUSPTO

Cancellation 92085317 at USPTO between Trek Bicycle Corporation and Electraveler LLC, over the mark ELECTRAVELER, filed Jun 3, 2024. Status in the office record: other.

View ELECTRAVELERGet this data via the API
Status
Other
Result
Other
Filed
Jun 3, 2024
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Petitioner

Trek Bicycle Corporation

Company trademarks
Respondent

Electraveler LLC

Timeline

How the case has moved

Dates from the USPTO record and the ELECTRAVELER filing.

  1. ELECTRAVELER filed

    Application 97248369 filed at the USPTO.

  2. ELECTRAVELER registered

  3. Cancellation filed

    Trek Bicycle Corporation started cancellation 92085317 at USPTO against ELECTRAVELER.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
ELECTRAVELERContested97248369USPTO
ELECTRA BICYCLE COMPANYRelied on74588555USPTO
ELECTRA BICYCLE COMPANYRelied on74588556USPTO
ELECTRARelied on86173619USPTO
ELECTRARelied on86609824USPTO
ELECTRARelied on86798489USPTO
ELECTRARelied on90611869USPTO
ELECTRARelied on97472180USPTO
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_6bb3f96e-e2fb-413a-b341-1cb908f9f04a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6bb3f96e-e2fb-413a-b341-1cb908f9f04a",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92085317",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-06-03",
  "parties": [
    {
      "name": "Trek Bicycle Corporation",
      "role": "petitioner"
    },
    {
      "name": "Electraveler LLC",
      "role": "respondent"
    }
  ]
}