Cancellation · USPTO

Cancellation 92081318

OtherUSPTO

Cancellation 92081318 at USPTO between New Prime, Inc. d/b/a Prime Inc. and Prime Group Logistics Holding, LLC, over the mark PRIME GROUP LOGISTICS HOLDING, filed Jan 6, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 6, 2023
Marks involved
4
Parties

Who is involved

The parties as named in the office record.

Petitioner

New Prime, Inc. d/b/a Prime Inc.

Respondent

Prime Group Logistics Holding, LLC

Timeline

How the case has moved

Dates from the USPTO record and the PRIME GROUP LOGISTICS HOLDING filing.

  1. PRIME GROUP LOGISTICS HOLDING filed

    Application 87705180 filed at the USPTO.
  2. PRIME GROUP LOGISTICS HOLDING registered

  3. Cancellation filed

    New Prime, Inc. d/b/a Prime Inc. started cancellation 92081318 at USPTO against PRIME GROUP LOGISTICS HOLDING.
Marks

Marks involved

1 contested mark, 3 marks the challenger relies on.

MarkRoleApplicationOffice
PRIME GROUP LOGISTICS HOLDINGContested87705180USPTO
PRIME INC.Relied on87575242USPTO
PRIME LOGISTICSRelied on87586259USPTO
POWERONLY ADVANCED FLEET PROGRAM BY PRIME INC.Relied on90498637USPTO
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_1be7d93a-a540-4623-afbf-7a247c61e84c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1be7d93a-a540-4623-afbf-7a247c61e84c",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92081318",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-01-06",
  "parties": [
    {
      "name": "New Prime, Inc. d/b/a Prime Inc.",
      "role": "petitioner"
    },
    {
      "name": "Prime Group Logistics Holding, LLC",
      "role": "respondent"
    }
  ]
}