Opposition · USPTO

Opposition 91241800

OtherUSPTO

Opposition 91241800 at USPTO between Karsten Manufacturing Corporation and Pingle Inc. AKA Pingle, over the mark PINGLE, filed Jun 13, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 13, 2018
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

Karsten Manufacturing Corporation

Company trademarks
Respondent

Pingle Inc. AKA Pingle

Timeline

How the case has moved

Dates from the USPTO record and the PINGLE filing.

  1. PINGLE filed

    Application 87626885 filed at the USPTO.
  2. Opposition filed

    Karsten Manufacturing Corporation started opposition 91241800 at USPTO against PINGLE.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
PINGLEContested87626885USPTO
PINGRelied on73803028USPTO
PINGRelied on73810646USPTO
PINGRelied on74018761USPTO
PINGRelied on76418345USPTO
PINGRelied on76418359USPTO
PINGRelied on76418361USPTO
PINGRelied on76418362USPTO
PINGRelied on76418701USPTO
PINGRelied on76418702USPTO
PINGRelied on77022878USPTO
PINGRelied on77043860USPTO

+38 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_c552482c-b396-4c82-9a6a-a3dee1ca4fda
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c552482c-b396-4c82-9a6a-a3dee1ca4fda",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91241800",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-06-13",
  "parties": [
    {
      "name": "Karsten Manufacturing Corporation",
      "role": "opponent"
    },
    {
      "name": "Pingle Inc. AKA Pingle",
      "role": "respondent"
    }
  ]
}