Opposition · USPTO

Opposition 91283891

OtherUSPTO

Opposition 91283891 at USPTO between Standard & Poor's Financial Services LLC and Plus500US Inc, over the mark PLUS500, filed Mar 10, 2023. Status in the office record: other.

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

Who is involved

The parties as named in the office record.

Opponent

Standard & Poor's Financial Services LLC

Respondent

Plus500US Inc

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the PLUS500 filing.

  1. PLUS500 filed

    Application 90404255 filed at the USPTO.
  2. Opposition filed

    Standard & Poor's Financial Services LLC started opposition 91283891 at USPTO against PLUS500.
Marks

Marks involved

2 contested marks, 7 marks the challenger relies on.

MarkRoleApplicationOffice
PLUS500Contested90404255USPTO
PLUS + 500Contested90404266USPTO
S&P 500Relied on73673838USPTO
S&P 500 LOW VOLATILITY INDEXRelied on85438358USPTO
S&P 500 DYNAMIC VEQTOR INDEXRelied on86172785USPTO
S&P 500 CATHOLIC VALUES INDEXRelied on86525854USPTO
S&P 500 VEQTORRelied on86606383USPTO
S&P CHINA 500Relied on87259308USPTO
S&P 500Relied on88414131USPTO
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_5ca20a44-84bd-4c3f-a3a9-181b78c17b02
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5ca20a44-84bd-4c3f-a3a9-181b78c17b02",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91283891",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-03-10",
  "parties": [
    {
      "name": "Standard & Poor's Financial Services LLC",
      "role": "opponent"
    },
    {
      "name": "Plus500US Inc",
      "role": "respondent"
    }
  ]
}