Opposition · USPTO

Opposition 91285269

OtherUSPTO

Opposition 91285269 at USPTO between Ampere Computing LLC and John Windmuller, over the mark AMPERE TRANSPORT, filed May 31, 2023. Status in the office record: other.

View AMPERE TRANSPORTGet this data via the API
Status
Other
Result
Other
Filed
May 31, 2023
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Ampere Computing LLC

Company trademarks
Respondent

John Windmuller

Timeline

How the case has moved

Dates from the USPTO record and the AMPERE TRANSPORT filing.

  1. AMPERE TRANSPORT filed

    Application 97017795 filed at the USPTO.

  2. Opposition filed

    Ampere Computing LLC started opposition 91285269 at USPTO against AMPERE TRANSPORT.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
AMPERE TRANSPORTContested97017795USPTO
AMPERERelied on87681720USPTO
AMPERE COMPUTINGRelied on87701332USPTO
AMPERE SEMICONDUCTORRelied on87701341USPTO
A AMPERERelied on87746757USPTO
AMPERERelied on87980846USPTO
A AMPERERelied on87982746USPTO
AMPERE ALTRARelied on88793492USPTO
AMPERE ALTRA MAXRelied on90008450USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_1c2aa4af-6140-4049-9b3f-8c2314ee432c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1c2aa4af-6140-4049-9b3f-8c2314ee432c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91285269",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-05-31",
  "parties": [
    {
      "name": "Ampere Computing LLC",
      "role": "opponent"
    },
    {
      "name": "John Windmuller",
      "role": "respondent"
    }
  ]
}