Opposition · USPTO

Opposition 91184224

OtherUSPTO

Opposition 91184224 at USPTO between SKF USA Inc. and Hangzhou Hengke Precision Machinery & Electronics Co., Ltd., over the mark SKH, filed May 20, 2008. Status in the office record: other.

View SKHGet this data via the API
Status
Other
Result
Other
Filed
May 20, 2008
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

SKF USA Inc.

Company trademarks
Respondent

Hangzhou Hengke Precision Machinery & Electronics Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the SKH filing.

  1. SKH filed

    Application 77327744 filed at the USPTO.

  2. Opposition filed

    SKF USA Inc. started opposition 91184224 at USPTO against SKH.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
SKHContested77327744USPTO
SKFRelied on71529098USPTO
SKFRelied on71529102USPTO
SKFRelied on72298294USPTO
SKFRelied on73195693USPTO
SKFRelied on73208090USPTO
SKFRelied on73395705USPTO
SKFRelied on73395714USPTO
SKFRelied on73396559USPTO
SKFRelied on73465292USPTO
SKFRelied on74302924USPTO
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_fd7d3523-77db-4be6-93f7-06776226a72d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fd7d3523-77db-4be6-93f7-06776226a72d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91184224",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-05-20",
  "parties": [
    {
      "name": "SKF USA Inc.",
      "role": "opponent"
    },
    {
      "name": "Hangzhou Hengke Precision Machinery & Electronics Co., Ltd.",
      "role": "respondent"
    }
  ]
}