Opposition · USPTO

Opposition 91300863

OtherUSPTO

Opposition 91300863 at USPTO between General Electric Company and Shenzhen YiyuanShengda Trade Co., Ltd., over the mark GETRAVEL, filed Aug 6, 2025. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 6, 2025
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

General Electric Company

Company trademarks
Respondent

Shenzhen YiyuanShengda Trade Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the GETRAVEL filing.

  1. GETRAVEL filed

    Application 98895318 filed at the USPTO.
  2. Opposition filed

    General Electric Company started opposition 91300863 at USPTO against GETRAVEL.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
GETRAVELContested98895318USPTO
GERelied on70035089USPTO
GERelied on73392934USPTO
GERelied on73392935USPTO
GERelied on74274901USPTO
GERelied on77028245USPTO
GERelied on77184621USPTO
GERelied on77184722USPTO
GE90Relied on78036148USPTO
GERelied on78067095USPTO
GERelied on78067098USPTO
GERelied on78067099USPTO

+38 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_98b0e04d-0e8d-4f12-9dd6-c1fad2228ed1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_98b0e04d-0e8d-4f12-9dd6-c1fad2228ed1",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91300863",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-08-06",
  "parties": [
    {
      "name": "General Electric Company",
      "role": "opponent"
    },
    {
      "name": "Shenzhen YiyuanShengda Trade Co., Ltd.",
      "role": "respondent"
    }
  ]
}