Cancellation · USPTO

Cancellation 92090691

SuspendedUSPTO

Cancellation 92090691 at USPTO between Transcendent Travel Services, LLC and Transcend Cruises Inc., over the mark TRANSCEND CRUISES, filed Jan 22, 2026. Status in the office record: suspended.

View TRANSCEND CRUISESGet this data via the API
Status
Suspended
Filed
Jan 22, 2026
Marks involved
3
Parties

Who is involved

The parties as named in the office record.

Petitioner

Transcendent Travel Services, LLC

Respondent

Transcend Cruises Inc.

Timeline

How the case has moved

Dates from the USPTO record and the TRANSCEND CRUISES filing.

  1. TRANSCEND CRUISES filed

    Application 99119227 filed at the USPTO.

  2. TRANSCEND CRUISES registered

  3. Cancellation filed

    Transcendent Travel Services, LLC started cancellation 92090691 at USPTO against TRANSCEND CRUISES.
  4. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 2 marks the challenger relies on.

MarkRoleApplicationOffice
TRANSCEND CRUISESContested99119227USPTO
TRANSCENDENT EXPERIENCE BASED TRAVELRelied on87536905USPTO
TRANSCENDENTRelied on97791612USPTO
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_a89df8b6-2d10-48b4-801b-9597479993fe
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a89df8b6-2d10-48b4-801b-9597479993fe",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92090691",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2026-01-22",
  "parties": [
    {
      "name": "Transcendent Travel Services, LLC",
      "role": "petitioner"
    },
    {
      "name": "Transcend Cruises Inc.",
      "role": "respondent"
    }
  ]
}