Opposition · USPTO

Opposition 91206501

OtherUSPTO

Opposition 91206501 at USPTO between Anheuser-Busch, LLC and Andrew Y Young, over the mark BUZ, filed Aug 9, 2012. Status in the office record: other.

View BUZGet this data via the API
Status
Other
Result
Other
Filed
Aug 9, 2012
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Anheuser-Busch, LLC

Respondent

Andrew Y Young

Timeline

How the case has moved

Dates from the USPTO record and the BUZ filing.

  1. BUZ filed

    Application 85514008 filed at the USPTO.

  2. Opposition filed

    Anheuser-Busch, LLC started opposition 91206501 at USPTO against BUZ.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
BUZContested85514008USPTO
BUDWEISERRelied on71009773USPTO
BUDRelied on72040799USPTO
THIS BUD'S FOR YOURelied on73368350USPTO
BUD LIGHTRelied on73386660USPTO
BUDRelied on73570808USPTO
BUD LIGHTRelied on73678356USPTO
THIS BUD'S FOR YOURelied on74035411USPTO
BUD KINGRelied on76245059USPTO
BUD LIGHT LIMERelied on77682302USPTO
GRAB SOME BUDSRelied on85108026USPTO
BUD LIGHT LIME LIME-A-RITARelied on85466756USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_63ffddfb-19c6-4e28-9f81-7e0d6ac5bc77
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_63ffddfb-19c6-4e28-9f81-7e0d6ac5bc77",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91206501",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-08-09",
  "parties": [
    {
      "name": "Anheuser-Busch, LLC",
      "role": "opponent"
    },
    {
      "name": "Andrew Y Young",
      "role": "respondent"
    }
  ]
}