Opposition · USPTO

Opposition 91305837

OtherUSPTO

Opposition 91305837 at USPTO between Fuente Marketing Ltd. and Costline trading INC, over the mark GERKX, filed Mar 11, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 11, 2026
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Fuente Marketing Ltd.

Respondent

Costline trading INC

Timeline

How the case has moved

Dates from the USPTO record and the GERKX filing.

  1. GERKX filed

    Application 99356158 filed at the USPTO.
  2. Opposition filed

    Fuente Marketing Ltd. started opposition 91305837 at USPTO against GERKX.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
GERKXContested99356158USPTO
FUENTE FUENTE OPUS "X"Relied on74550044USPTO
FUENTE OPUSXRelied on75857912USPTO
X TO THE THIRD POWERRelied on75859380USPTO
FORBIDDENXRelied on75982386USPTO
XRelied on77064649USPTO
XRelied on78524998USPTO
XXXRelied on78525491USPTO
PERFECXION XRelied on78525498USPTO
SERIEXRelied on78535250USPTO
RISING XRelied on78743747USPTO
FUENTE FUENTE FORBIDDEN XRelied on78906059USPTO

+6 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_c4a283ba-15e6-40e3-8494-e4116eaf0520
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c4a283ba-15e6-40e3-8494-e4116eaf0520",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91305837",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-03-11",
  "parties": [
    {
      "name": "Fuente Marketing Ltd.",
      "role": "opponent"
    },
    {
      "name": "Costline trading INC",
      "role": "respondent"
    }
  ]
}