Opposition · USPTO

Opposition 91215658

OtherUSPTO

Opposition 91215658 at USPTO between Beats Electronics LLC and Threaks GmbH, over the mark BEATBUDDY, filed Mar 31, 2014. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 31, 2014
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Beats Electronics LLC

Company trademarks
Respondent

Threaks GmbH

Timeline

How the case has moved

Dates from the USPTO record and the BEATBUDDY filing.

  1. BEATBUDDY filed

    Application 85717284 filed at the USPTO.
  2. Opposition filed

    Beats Electronics LLC started opposition 91215658 at USPTO against BEATBUDDY.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
BEATBUDDYContested85717284USPTO
BEATS BY DR. DRERelied on77786492USPTO
BEATSRelied on77980257USPTO
HEARTBEATSRelied on77980836USPTO
BEATSRelied on77982434USPTO
BEATS BY DR. DRERelied on77983185USPTO
IBEATSRelied on77983208USPTO
BEATSRelied on77983303USPTO
LIVE BEATSRelied on85035232USPTO
BEATS PRORelied on85057928USPTO
JUSTBEATSRelied on85072253USPTO
BEATS STUDIORelied on85554241USPTO

+8 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_3a05d948-d10f-47e2-b02e-80987ad3c35d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3a05d948-d10f-47e2-b02e-80987ad3c35d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91215658",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-03-31",
  "parties": [
    {
      "name": "Beats Electronics LLC",
      "role": "opponent"
    },
    {
      "name": "Threaks GmbH",
      "role": "respondent"
    }
  ]
}