Cancellation · USPTO

Cancellation 92074673

OtherUSPTO

Cancellation 92074673 at USPTO between Hub Group, Inc. and Hubtek, LLC, over the mark HUBTEK, filed Jul 10, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 10, 2020
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Petitioner

Hub Group, Inc.

Company trademarks
Respondent

Hubtek, LLC

Timeline

How the case has moved

Dates from the USPTO record and the HUBTEK filing.

  1. HUBTEK filed

    Application 88143589 filed at the USPTO.
  2. HUBTEK registered

  3. Cancellation filed

    Hub Group, Inc. started cancellation 92074673 at USPTO against HUBTEK.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
HUBTEKContested88143589USPTO
HUB GROUPRelied on75009059USPTO
H HUB GROUP TRUCKINGRelied on86248271USPTO
S HUB GROUP CAPACITY SOLUTIONSRelied on86713180USPTO
HUB GROUP CAPACITY SOLUTIONSRelied on86713200USPTO
HUBPRORelied on87018203USPTO
HUB GROUP DEDICATED SERVICESRelied on87464706USPTO
HUB GROUP DEDICATED SERVICESRelied on87464722USPTO
HUB GROUP DEDICATEDRelied on87470052USPTO
HUB GROUP DEDICATEDRelied on87470068USPTO
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_54ea99a1-6cb7-4ef4-9620-fc431e075b82
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_54ea99a1-6cb7-4ef4-9620-fc431e075b82",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92074673",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-07-10",
  "parties": [
    {
      "name": "Hub Group, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Hubtek, LLC",
      "role": "respondent"
    }
  ]
}