Opposition · USPTO

Opposition 91278036

OtherUSPTO

Opposition 91278036 at USPTO between Riot Games, Inc. and T2M, LLC, over the mark RIOT PWR, filed Aug 17, 2022. Status in the office record: other.

View RIOT PWRGet this data via the API
Status
Other
Result
Other
Filed
Aug 17, 2022
Marks involved
25
Parties

Who is involved

The parties as named in the office record.

Opponent

Riot Games, Inc.

Respondent

T2M, LLC

Timeline

How the case has moved

Dates from the USPTO record and the RIOT PWR filing.

  1. RIOT PWR filed

    Application 90780248 filed at the USPTO.

  2. Opposition filed

    Riot Games, Inc. started opposition 91278036 at USPTO against RIOT PWR.
Marks

Marks involved

3 contested marks, 22 marks the challenger relies on.

MarkRoleApplicationOffice
RIOT PWRContested90780248USPTO
RIOT PWRContested90780311USPTO
RIOT PWRContested97129377USPTO
RIOT GAMESRelied on77058994USPTO
RIOTRelied on77059016USPTO
RIOT GAMESRelied on77982952USPTO
RIOT POINTSRelied on85430234USPTO
RIOT GAMESRelied on85567079USPTO
RIOT GAMESRelied on85567105USPTO
RIOT PINRelied on85749345USPTO
RIOT GAMESRelied on88387301USPTO
RIOT GAMESRelied on88387305USPTO

+13 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_59a69cb8-5490-4e99-9629-40d07b44f325
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_59a69cb8-5490-4e99-9629-40d07b44f325",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91278036",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-08-17",
  "parties": [
    {
      "name": "Riot Games, Inc.",
      "role": "opponent"
    },
    {
      "name": "T2M, LLC",
      "role": "respondent"
    }
  ]
}