Opposition · USPTO

Opposition 91275098

OtherUSPTO

Opposition 91275098 at USPTO between Intel Corporation and ARC Document Solutions, LLC, over the mark BUILTINTEL, filed Mar 9, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 9, 2022
Marks involved
33
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Company trademarks
Respondent

ARC Document Solutions, LLC

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the BUILTINTEL filing.

  1. BUILTINTEL filed

    Application 88899403 filed at the USPTO.
  2. Opposition filed

    Intel Corporation started opposition 91275098 at USPTO against BUILTINTEL.
Marks

Marks involved

1 contested mark, 32 marks the challenger relies on.

MarkRoleApplicationOffice
BUILTINTELContested88899403USPTO
INTELRelied on72384319USPTO
INTELRelied on72384320USPTO
INTELRelied on73035122USPTO
INTELRelied on74225506USPTO
INTELRelied on74225623USPTO
INTELRelied on75160105USPTO
INTELRelied on75160106USPTO
INTELRelied on75163576USPTO
INTELRelied on75349837USPTO
INTELRelied on75371362USPTO
INTELRelied on75371363USPTO

+21 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_bd9fdae5-4514-47ea-b17f-87b727e7cb1d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bd9fdae5-4514-47ea-b17f-87b727e7cb1d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91275098",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-03-09",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "ARC Document Solutions, LLC",
      "role": "respondent"
    }
  ]
}