Opposition · USPTO

Opposition 91301273

OtherUSPTO

Opposition 91301273 at USPTO between Lyft, Inc. and Lift Me Up LLC, over the mark LIFT ME UP, filed Aug 26, 2025. Status in the office record: other.

View LIFT ME UPGet this data via the API
Status
Other
Result
Other
Filed
Aug 26, 2025
Marks involved
35
Parties

Who is involved

The parties as named in the office record.

Opponent

Lyft, Inc.

Company trademarks
Respondent

Lift Me Up LLC

Timeline

How the case has moved

Dates from the USPTO record and the LIFT ME UP filing.

  1. LIFT ME UP filed

    Application 98775359 filed at the USPTO.

  2. Opposition filed

    Lyft, Inc. started opposition 91301273 at USPTO against LIFT ME UP.
Marks

Marks involved

1 contested mark, 34 marks the challenger relies on.

MarkRoleApplicationOffice
LIFT ME UPContested98775359USPTO
LYFTRelied on85743120USPTO
LYFTRelied on86183222USPTO
LYFTRelied on86183253USPTO
LYFTRelied on86183891USPTO
LYFTRelied on86183906USPTO
LYFTRelied on87254350USPTO
LYFT SCOOTERSRelied on88041722USPTO
LYFTRelied on88041743USPTO
LYFTRelied on88355902USPTO
LYFT DIRECTRelied on88356643USPTO
LYFT CONCIERGERelied on88435433USPTO

+23 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_0af53c0f-5a7a-42bf-b0e4-5e73ab44f366
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0af53c0f-5a7a-42bf-b0e4-5e73ab44f366",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91301273",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-08-26",
  "parties": [
    {
      "name": "Lyft, Inc.",
      "role": "opponent"
    },
    {
      "name": "Lift Me Up LLC",
      "role": "respondent"
    }
  ]
}