Cancellation · USPTO

Cancellation 92055955

OtherUSPTO

Cancellation 92055955 at USPTO between BHPC Associates LLC and Royal County of Berkshire Polo Club Ltd., over the mark ROYAL BERKSHIRE POLO CLUB, filed Jul 31, 2012. Status in the office record: other.

View ROYAL BERKSHIRE POLO CLUBGet this data via the API
Status
Other
Result
Other
Filed
Jul 31, 2012
Marks involved
3
Parties

Who is involved

The parties as named in the office record.

Petitioner

BHPC Associates LLC

Company trademarks
Respondent

Royal County of Berkshire Polo Club Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the ROYAL BERKSHIRE POLO CLUB filing.

  1. ROYAL BERKSHIRE POLO CLUB filed

    Application 78980858 filed at the USPTO.

  2. ROYAL BERKSHIRE POLO CLUB registered

  3. Cancellation filed

    BHPC Associates LLC started cancellation 92055955 at USPTO against ROYAL BERKSHIRE POLO CLUB.
Marks

Marks involved

1 contested mark, 2 marks the challenger relies on.

MarkRoleApplicationOffice
ROYAL BERKSHIRE POLO CLUBContested78980858USPTO
BEVERLY HILLS POLO CLUBRelied on74209022USPTO
BEVERLY HILLS POLO CLUBRelied on75162739USPTO
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_fb5820d5-c609-475e-aed4-df7813708d7c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fb5820d5-c609-475e-aed4-df7813708d7c",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92055955",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-07-31",
  "parties": [
    {
      "name": "BHPC Associates LLC",
      "role": "petitioner"
    },
    {
      "name": "Royal County of Berkshire Polo Club Ltd.",
      "role": "respondent"
    }
  ]
}