Opposition · USPTO

Opposition 91226225

OtherUSPTO

Opposition 91226225 at USPTO between Anheuser-Busch, LLC and Bud Music, LLC DBA Bud, over the mark BUD, filed Feb 8, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 8, 2016
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Anheuser-Busch, LLC

Respondent

Bud Music, LLC DBA Bud

Timeline

How the case has moved

Dates from the USPTO record and the BUD filing.

  1. BUD filed

    Application 86555400 filed at the USPTO.
  2. Opposition filed

    Anheuser-Busch, LLC started opposition 91226225 at USPTO against BUD.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
BUDContested86555400USPTO
BUDWEISERRelied on71009773USPTO
BUDRelied on72040799USPTO
THIS BUD'S FOR YOURelied on73368350USPTO
BUD LIGHTRelied on73386660USPTO
BUDWEISERRelied on76488792USPTO
BUD LIGHT LIMERelied on77682302USPTO
GRAB SOME BUDSRelied on85108026USPTO
TRACK YOUR BUDRelied on85466410USPTO
BUDWEISERRelied on86051443USPTO
BUDWEISER SCENESTERRelied on86058272USPTO
BUDS FOR BUDSRelied on86406872USPTO

+1 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_501f19bb-163a-49cc-a997-b9f23572192e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_501f19bb-163a-49cc-a997-b9f23572192e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91226225",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-02-08",
  "parties": [
    {
      "name": "Anheuser-Busch, LLC",
      "role": "opponent"
    },
    {
      "name": "Bud Music, LLC DBA Bud",
      "role": "respondent"
    }
  ]
}