Opposition · USPTO

Opposition 91206321

OtherUSPTO

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

Status
Other
Result
Other
Filed
Jul 31, 2012
Marks involved
5
Parties

Who is involved

The parties as named in the office record.

Opponent

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 COUNTY OF BERKSHIRE POLO CLUB filing.

  1. ROYAL COUNTY OF BERKSHIRE POLO CLUB filed

    Application 85224666 filed at the USPTO.
  2. Opposition filed

    BHPC Associates LLC started opposition 91206321 at USPTO against ROYAL COUNTY OF BERKSHIRE POLO CLUB.
Marks

Marks involved

1 contested mark, 4 marks the challenger relies on.

MarkRoleApplicationOffice
ROYAL COUNTY OF BERKSHIRE POLO CLUBContested85224666USPTO
BEVERLY HILLS POLO CLUBRelied on73568042USPTO
BEVERLY HILLS POLO CLUBRelied on74209022USPTO
BEVERLY HILLS POLO CLUBRelied on74558586USPTO
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 /v1/proceedings/{id}
ID=prc_af1ce55c-ba44-459c-bc16-ddcb7d4f1b9c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_af1ce55c-ba44-459c-bc16-ddcb7d4f1b9c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91206321",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-07-31",
  "parties": [
    {
      "name": "BHPC Associates LLC",
      "role": "opponent"
    },
    {
      "name": "Royal County of Berkshire Polo Club Ltd.",
      "role": "respondent"
    }
  ]
}