Opposition · USPTO

Opposition 91274274

OtherUSPTO

Opposition 91274274 at USPTO between TE Connectivity Services GmbH and Amptyco Co., Limited, over the mark AMPTYCO, filed Feb 1, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 1, 2022
Marks involved
24
Parties

Who is involved

The parties as named in the office record.

Opponent

TE Connectivity Services GmbH

Respondent

Amptyco Co., Limited

Timeline

How the case has moved

Dates from the USPTO record and the AMPTYCO filing.

  1. AMPTYCO filed

    Application 90485453 filed at the USPTO.
  2. Opposition filed

    TE Connectivity Services GmbH started opposition 91274274 at USPTO against AMPTYCO.
Marks

Marks involved

2 contested marks, 22 marks the challenger relies on.

MarkRoleApplicationOffice
AMPTYCOContested90485453USPTO
AMPTYCOContested90488171USPTO
AMPRelied on71616197USPTO
AMPSEALRelied on72018395USPTO
AMPOWERRelied on72030631USPTO
AMPLIVARRelied on72030632USPTO
AMP EDGERelied on72083422USPTO
AMP-BLADERelied on72117425USPTO
AMP-LEAFRelied on72118030USPTO
AMPACTRelied on72158896USPTO
AMP-TABRelied on72177326USPTO
AMPACTRelied on72195265USPTO

+12 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_8dda5442-d3fe-4129-8762-f2978092c0f9
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8dda5442-d3fe-4129-8762-f2978092c0f9",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91274274",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-02-01",
  "parties": [
    {
      "name": "TE Connectivity Services GmbH",
      "role": "opponent"
    },
    {
      "name": "Amptyco Co., Limited",
      "role": "respondent"
    }
  ]
}