Opposition · USPTO

Opposition 91269121

OtherUSPTO

Opposition 91269121 at USPTO between King.com Limited and The Creative Assembly Limited, over the mark TOTAL WAR SAGA: TROY, filed Apr 26, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 26, 2021
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

King.com Limited

Company trademarks
Respondent

The Creative Assembly Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the TOTAL WAR SAGA: TROY filing.

  1. TOTAL WAR SAGA: TROY filed

    Application 79285824 filed at the USPTO.
  2. Opposition filed

    King.com Limited started opposition 91269121 at USPTO against TOTAL WAR SAGA: TROY.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
TOTAL WAR SAGA: TROYContested79285824USPTO
SAGARelied on85482736USPTO
BUBBLE SAGARelied on85482741USPTO
BUBBLE WITCH SAGARelied on85482745USPTO
PUZZLE SAGARelied on85482751USPTO
CANDY CRUSH SAGARelied on85566839USPTO
PET RESCUE SAGARelied on85751362USPTO
FARM HEROES SAGARelied on85904572USPTO
SODA SAGARelied on86413844USPTO
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_bc1c6a36-8224-4d53-ac97-d2816b2e2880
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bc1c6a36-8224-4d53-ac97-d2816b2e2880",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91269121",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-04-26",
  "parties": [
    {
      "name": "King.com Limited",
      "role": "opponent"
    },
    {
      "name": "The Creative Assembly Limited",
      "role": "respondent"
    }
  ]
}