Opposition · USPTO

Opposition 91302726

OtherUSPTO

Opposition 91302726 at USPTO between Ford Motor Company and Shenzhen Qisheng Technology Co., LTD, over the mark LINHAMCOLN, filed Oct 28, 2025. Status in the office record: other.

View LINHAMCOLNGet this data via the API
Status
Other
Result
Other
Filed
Oct 28, 2025
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Ford Motor Company

Company trademarks
Respondent

Shenzhen Qisheng Technology Co., LTD

Timeline

How the case has moved

Dates from the USPTO record and the LINHAMCOLN filing.

  1. LINHAMCOLN filed

    Application 98897693 filed at the USPTO.

  2. Opposition filed

    Ford Motor Company started opposition 91302726 at USPTO against LINHAMCOLN.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
LINHAMCOLNContested98897693USPTO
LINCOLNRelied on71544440USPTO
LINCOLNRelied on75077984USPTO
LINCOLNRelied on85057575USPTO
LINCOLNRelied on85264207USPTO
LINCOLN CONNECTRelied on87541356USPTO
LINCOLN CO-PILOT360Relied on87746746USPTO
LINCOLNRelied on90733275USPTO
LINCOLNRelied on97577179USPTO
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_b55ebf8c-af5f-4899-bcdd-49bf324bf99a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_b55ebf8c-af5f-4899-bcdd-49bf324bf99a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302726",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-10-28",
  "parties": [
    {
      "name": "Ford Motor Company",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Qisheng Technology Co., LTD",
      "role": "respondent"
    }
  ]
}