Opposition · USPTO

Opposition 91302330

OtherUSPTO

Opposition 91302330 at USPTO between Intel Corporation and Axin Luo, over the mark INTELBRAS, filed Oct 10, 2025. Status in the office record: other.

View INTELBRASGet this data via the API
Status
Other
Result
Other
Filed
Oct 10, 2025
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Company trademarks
Respondent

Axin Luo

Timeline

How the case has moved

Dates from the USPTO record and the INTELBRAS filing.

  1. INTELBRAS filed

    Application 99050131 filed at the USPTO.

  2. Opposition filed

    Intel Corporation started opposition 91302330 at USPTO against INTELBRAS.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
INTELBRASContested99050131USPTO
INTELRelied on72384319USPTO
INTELRelied on72384320USPTO
INTELRelied on73035122USPTO
INTEL INSIDERelied on74159673USPTO
INTEL INSIDERelied on75160103USPTO
INTELRelied on75160106USPTO
INTELRelied on75163576USPTO
INTELRelied on75412490USPTO
INTELRelied on75412493USPTO
INTELRelied on76975693USPTO
INTEL ATOMRelied on77406712USPTO

+7 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_5180dff3-4a64-431b-a1b8-385e6a7ad411
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5180dff3-4a64-431b-a1b8-385e6a7ad411",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91302330",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-10-10",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "Axin Luo",
      "role": "respondent"
    }
  ]
}