Opposition · USPTO

Opposition 91252512

OtherUSPTO

Opposition 91252512 at USPTO between Target Brands, Inc. and Soctronics Inc., over the mark A, filed Nov 25, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Nov 25, 2019
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Target Brands, Inc.

Company trademarks
Respondent

Soctronics Inc.

Timeline

How the case has moved

Dates from the USPTO record and the A filing.

  1. A filed

    Application 88183182 filed at the USPTO.
  2. Opposition filed

    Target Brands, Inc. started opposition 91252512 at USPTO against A.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
AContested88183182USPTO
[Design mark]Relied on72425130USPTO
[Design mark]Relied on76052624USPTO
[Design mark]Relied on76379844USPTO
[Design mark]Relied on76379845USPTO
[Design mark]Relied on76379846USPTO
[Design mark]Relied on76379848USPTO
[Design mark]Relied on76379849USPTO
[Design mark]Relied on76379949USPTO
[Design mark]Relied on76387394USPTO
[Design mark]Relied on76418295USPTO
[Design mark]Relied on77982272USPTO

+7 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_63865a1e-0b4c-49f8-bbd6-f3947d1d91a3
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_63865a1e-0b4c-49f8-bbd6-f3947d1d91a3",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91252512",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-11-25",
  "parties": [
    {
      "name": "Target Brands, Inc.",
      "role": "opponent"
    },
    {
      "name": "Soctronics Inc.",
      "role": "respondent"
    }
  ]
}