Opposition · USPTO

Opposition 91308877

PendingUSPTO

Opposition 91308877 at USPTO between Carma Laboratories, Inc. and Cimed & Co. S.A., over the mark CARMED, filed Jul 15, 2026. Status in the office record: pending.

View CARMEDGet this data via the API
Status
Pending
Filed
Jul 15, 2026
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Carma Laboratories, Inc.

Company trademarks
Respondent

Cimed & Co. S.A.

Timeline

How the case has moved

Dates from the USPTO record and the CARMED filing.

  1. CARMED filed

    Application 99406273 filed at the USPTO.

  2. Opposition filed

    Carma Laboratories, Inc. started opposition 91308877 at USPTO against CARMED.
  3. Next

    Awaiting decision

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
CARMEDContested99406273USPTO
CARMEXRelied on75168480USPTO
CARMEXRelied on77641191USPTO
CARMEX COMFORT CARERelied on86888405USPTO
CARMEX DAILY CARERelied on86934493USPTO
CARMEXRelied on87050617USPTO
CARMEX DAILY CARERelied on87050627USPTO
CARMEX COMFORT CARERelied on87050635USPTO
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_1fad9720-eefa-4f24-95c3-4223d1248bef
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1fad9720-eefa-4f24-95c3-4223d1248bef",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91308877",
  "status": "pending",
  "office_code": "US",
  "filed_date": "2026-07-15",
  "parties": [
    {
      "name": "Carma Laboratories, Inc.",
      "role": "opponent"
    },
    {
      "name": "Cimed & Co. S.A.",
      "role": "respondent"
    }
  ]
}