Opposition · USPTO

Opposition 91240790

OtherUSPTO

Opposition 91240790 at USPTO between The Insights Group Limited and John W. Nickel, over the mark INSIGHT-DRIVEN CONSULTING, filed Apr 23, 2018. Status in the office record: other.

View INSIGHT-DRIVEN CONSULTINGGet this data via the API
Status
Other
Result
Other
Filed
Apr 23, 2018
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

The Insights Group Limited

Respondent

John W. Nickel

Timeline

How the case has moved

Dates from the USPTO record and the INSIGHT-DRIVEN CONSULTING filing.

  1. INSIGHT-DRIVEN CONSULTING filed

    Application 87395261 filed at the USPTO.

  2. Opposition filed

    The Insights Group Limited started opposition 91240790 at USPTO against INSIGHT-DRIVEN CONSULTING.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
INSIGHT-DRIVEN CONSULTINGContested87395261USPTO
INSIGHTSRelied on77464026USPTO
INSIGHTS DISCOVERYRelied on77464077USPTO
INSIGHTS NAVIGATORRelied on77464183USPTO
INSIGHTS NAVIGATORRelied on77464258USPTO
INSIGHTSRelied on77464297USPTO
INSIGHTS DISCOVERYRelied on77464322USPTO
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_dad3572a-cca6-4718-ac54-3832c5f09c5d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_dad3572a-cca6-4718-ac54-3832c5f09c5d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91240790",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-04-23",
  "parties": [
    {
      "name": "The Insights Group Limited",
      "role": "opponent"
    },
    {
      "name": "John W. Nickel",
      "role": "respondent"
    }
  ]
}