Opposition · USPTO

Opposition 91212208

OtherUSPTO

Opposition 91212208 at USPTO between Hostess Brands, LLC and Justin Sobodash, over the mark HOSTESS, filed Aug 28, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 28, 2013
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Hostess Brands, LLC

Company trademarks
Respondent

Justin Sobodash

Timeline

How the case has moved

Dates from the USPTO record and the HOSTESS filing.

  1. HOSTESS filed

    Application 85781823 filed at the USPTO.
  2. Opposition filed

    Hostess Brands, LLC started opposition 91212208 at USPTO against HOSTESS.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
HOSTESSContested85781823USPTO
HOSTESSRelied on71115132USPTO
HOSTESSRelied on72110601USPTO
HOSTESSRelied on72122166USPTO
HOSTESSRelied on73758150USPTO
HOSTESSRelied on74263606USPTO
HOSTESSRelied on74527325USPTO
HOSTESS 100 CALORIE PACKSRelied on77241096USPTO
HOSTESSRelied on77325871USPTO
LAS DELICIAS DE HOSTESSRelied on78785924USPTO
HOSTESSRelied on78958898USPTO
HOSTESS DIRECTRelied on85296105USPTO

+2 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_e3820f05-c628-49c6-aec9-28a896e7ac97
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e3820f05-c628-49c6-aec9-28a896e7ac97",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91212208",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-08-28",
  "parties": [
    {
      "name": "Hostess Brands, LLC",
      "role": "opponent"
    },
    {
      "name": "Justin Sobodash",
      "role": "respondent"
    }
  ]
}