Opposition · USPTO

Opposition 91271251

OtherUSPTO

Opposition 91271251 at USPTO between Target Brands, Inc. and Samuel P Hunter, over the mark ON TARGET TEAMS, filed Aug 25, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 25, 2021
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Target Brands, Inc.

Company trademarks
Respondent

Samuel P Hunter

Timeline

How the case has moved

Dates from the USPTO record and the ON TARGET TEAMS filing.

  1. ON TARGET TEAMS filed

    Application 88697908 filed at the USPTO.
  2. Opposition filed

    Target Brands, Inc. started opposition 91271251 at USPTO against ON TARGET TEAMS.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
ON TARGET TEAMSContested88697908USPTO
TARGETRelied on72276713USPTO
TARGETRelied on72276714USPTO
[Design mark]Relied on72425130USPTO
TARGETRelied on73495553USPTO
[Design mark]Relied on76052624USPTO
TARGETRelied on76418297USPTO
SUPER TARGETRelied on76460311USPTO
TARGETRelied on76473313USPTO
TARGETRelied on78897761USPTO
SUPER TARGETRelied on78923506USPTO
[Design mark]Relied on85031119USPTO
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_ed81044d-49ba-4180-a0f5-119e85f1328e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ed81044d-49ba-4180-a0f5-119e85f1328e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91271251",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-08-25",
  "parties": [
    {
      "name": "Target Brands, Inc.",
      "role": "opponent"
    },
    {
      "name": "Samuel P Hunter",
      "role": "respondent"
    }
  ]
}