Cancellation · USPTO

Cancellation 92061032

OtherUSPTO

Cancellation 92061032 at USPTO between The Ohio State University and The Poison Nut LLC dba The Poison Nut, over the mark THE POISON NUT, filed Mar 10, 2015. Status in the office record: other.

View THE POISON NUTGet this data via the API
Status
Other
Result
Other
Filed
Mar 10, 2015
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Petitioner

The Ohio State University

Respondent

The Poison Nut LLC dba The Poison Nut

Timeline

How the case has moved

Dates from the USPTO record and the THE POISON NUT filing.

  1. THE POISON NUT filed

    Application 85554270 filed at the USPTO.

  2. THE POISON NUT registered

  3. Cancellation filed

    The Ohio State University started cancellation 92061032 at USPTO against THE POISON NUT.
Marks

Marks involved

4 contested marks, 2 marks the challenger relies on.

MarkRoleApplicationOffice
THE POISON NUTContested85554270USPTO
THE POISONOUS NUTContested85554274USPTO
[Design mark]Contested86244448USPTO
THE POIS N NUTContested86261045USPTO
BUCKEYESRelied on73042963USPTO
BUCKEYESRelied on73394200USPTO
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_7b35fc15-5eb4-45f5-8b1a-b94964ada458
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7b35fc15-5eb4-45f5-8b1a-b94964ada458",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92061032",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-03-10",
  "parties": [
    {
      "name": "The Ohio State University",
      "role": "petitioner"
    },
    {
      "name": "The Poison Nut LLC dba The Poison Nut",
      "role": "respondent"
    }
  ]
}