Opposition · USPTO

Opposition 91283861

OtherUSPTO

Opposition 91283861 at USPTO between The Trustees of the Carroll Hall Shelby Trust and William Baron, over the mark SHELBY AVENUE, filed Mar 8, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 8, 2023
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

The Trustees of the Carroll Hall Shelby Trust

Respondent

William Baron

Timeline

How the case has moved

Dates from the USPTO record and the SHELBY AVENUE filing.

  1. SHELBY AVENUE filed

    Application 97240705 filed at the USPTO.
  2. Opposition filed

    The Trustees of the Carroll Hall Shelby Trust started opposition 91283861 at USPTO against SHELBY AVENUE.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
SHELBY AVENUEContested97240705USPTO
SHELBYFESTRelied on76699515USPTO
SHELBY GT-HRelied on78876659USPTO
CS SHELBYRelied on85816089USPTO
CARROLL SHELBY RACINGRelied on88137276USPTO
CS CARROLL SHELBY RACINGRelied on88137286USPTO
SHELBYRelied on88723824USPTO
CARROLL SHELBYRelied on88725103USPTO
SHELBY AMERICANRelied on88725594USPTO
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_77f6283c-2a54-4ddb-bf4c-783469b94cae
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_77f6283c-2a54-4ddb-bf4c-783469b94cae",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283861",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-03-08",
  "parties": [
    {
      "name": "The Trustees of the Carroll Hall Shelby Trust",
      "role": "opponent"
    },
    {
      "name": "William Baron",
      "role": "respondent"
    }
  ]
}