Cancellation · USPTO

Cancellation 92051165

OtherUSPTO

Cancellation 92051165 at USPTO between Anheuser-Busch, Incorporated and Roy Juarez, Jr., over the mark JOE BUD, filed Jun 29, 2009. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 29, 2009
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Petitioner

Anheuser-Busch, Incorporated

Respondent

Roy Juarez, Jr.

Timeline

How the case has moved

Dates from the USPTO record and the JOE BUD filing.

  1. JOE BUD filed

    Application 77310520 filed at the USPTO.
  2. JOE BUD registered

  3. Cancellation filed

    Anheuser-Busch, Incorporated started cancellation 92051165 at USPTO against JOE BUD.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
JOE BUDContested77310520USPTO
BUDWEISERRelied on71009773USPTO
BUDRelied on72040799USPTO
BUD MANRelied on73015113USPTO
BUD LIGHTRelied on73386660USPTO
BUDWEISERRelied on73523978USPTO
BUDRelied on73570808USPTO
BUD LIGHTRelied on73678356USPTO
BUDWEISERRelied on73711006USPTO
BUD BOWLRelied on73778954USPTO
BUD BOWLRelied on73783444USPTO
BUD MANRelied on78854638USPTO
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_3841c22b-7f1f-4e91-bc17-e048c5fbe027
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3841c22b-7f1f-4e91-bc17-e048c5fbe027",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92051165",
  "status": "other",
  "office_code": "US",
  "filed_date": "2009-06-29",
  "parties": [
    {
      "name": "Anheuser-Busch, Incorporated",
      "role": "petitioner"
    },
    {
      "name": "Roy Juarez, Jr.",
      "role": "respondent"
    }
  ]
}