Opposition · USPTO

Opposition 91213590

OtherUSPTO

Opposition 91213590 at USPTO between Beats Electronics, LLC and Beat Club Band, over the mark BEAT CLUB, filed Nov 20, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 20, 2013
Marks involved
21
Parties

Who is involved

The parties as named in the office record.

Opponent

Beats Electronics, LLC

Company trademarks
Respondent

Beat Club Band

Timeline

How the case has moved

Dates from the USPTO record and the BEAT CLUB filing.

  1. BEAT CLUB filed

    Application 85687012 filed at the USPTO.
  2. Opposition filed

    Beats Electronics, LLC started opposition 91213590 at USPTO against BEAT CLUB.
Marks

Marks involved

1 contested mark, 20 marks the challenger relies on.

MarkRoleApplicationOffice
BEAT CLUBContested85687012USPTO
BEATSRelied on77786522USPTO
CLUB BEATSRelied on77837774USPTO
BEATSAUDIORelied on77960477USPTO
BEATSRelied on77980257USPTO
HEARTBEATSRelied on77980836USPTO
BEATSRelied on77982434USPTO
BEATS BY DR. DRERelied on77983185USPTO
IBEATSRelied on77983208USPTO
BEATBOXRelied on85020116USPTO
LIVE BEATSRelied on85035232USPTO
MYBEATSRelied on85087126USPTO

+9 more marks in this case

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_63bf5435-d999-41ef-9413-cdc5b6bf9736
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_63bf5435-d999-41ef-9413-cdc5b6bf9736",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91213590",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-11-20",
  "parties": [
    {
      "name": "Beats Electronics, LLC",
      "role": "opponent"
    },
    {
      "name": "Beat Club Band",
      "role": "respondent"
    }
  ]
}