Opposition · USPTO

Opposition 91294667

OtherUSPTO

Opposition 91294667 at USPTO between Beats Electronics, LLC and Motinn, Inc., over the mark BEATBEST, filed Oct 21, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 21, 2024
Marks involved
22
Parties

Who is involved

The parties as named in the office record.

Opponent

Beats Electronics, LLC

Company trademarks
Respondent

Motinn, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the BEATBEST filing.

  1. BEATBEST filed

    Application 98178740 filed at the USPTO.
  2. Opposition filed

    Beats Electronics, LLC started opposition 91294667 at USPTO against BEATBEST.
Marks

Marks involved

1 contested mark, 21 marks the challenger relies on.

MarkRoleApplicationOffice
BEATBESTContested98178740USPTO
BEATSRelied on77664171USPTO
BEATS BY DR. DRERelied on77786492USPTO
BEATSRelied on77786522USPTO
BEATSRelied on77980257USPTO
BEATSRelied on77982434USPTO
BEATS BY DR. DRERelied on77983185USPTO
BEATSRelied on77983303USPTO
BEATS BY DR. DRERelied on77983608USPTO
BEATS STUDIORelied on85554241USPTO
BEATS PRORelied on85976944USPTO
URBEATSRelied on85978526USPTO

+10 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_3180f577-55de-4941-abe3-8809a29d11de
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3180f577-55de-4941-abe3-8809a29d11de",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91294667",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-10-21",
  "parties": [
    {
      "name": "Beats Electronics, LLC",
      "role": "opponent"
    },
    {
      "name": "Motinn, Inc.",
      "role": "respondent"
    }
  ]
}