Opposition · USPTO

Opposition 91292439

OtherUSPTO

Opposition 91292439 at USPTO between Golo, LLC and Guangdong Qiyue Future Technology Co., Ltd., over the mark GOSO, filed Jul 2, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 2, 2024
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Golo, LLC

Company trademarks
Respondent

Guangdong Qiyue Future Technology Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the GOSO filing.

  1. GOSO filed

    Application 98116634 filed at the USPTO.
  2. Opposition filed

    Golo, LLC started opposition 91292439 at USPTO against GOSO.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
GOSOContested98116634USPTO
GOLORelied on85374201USPTO
GOLO FOR LIFERelied on85380655USPTO
GOLORelied on87075500USPTO
MYGOLORelied on87076408USPTO
GOLO SMART CARDRelied on87088646USPTO
GOLORelied on87439564USPTO
GOLORelied on87858964USPTO
GOLORelied on87978072USPTO
GOLORelied on90850117USPTO
GOLORelied on97098983USPTO
GOLORelied on97098987USPTO

+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_02f9f32a-1d79-415f-bb81-61a30b1ed9b0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_02f9f32a-1d79-415f-bb81-61a30b1ed9b0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91292439",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-07-02",
  "parties": [
    {
      "name": "Golo, LLC",
      "role": "opponent"
    },
    {
      "name": "Guangdong Qiyue Future Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}