Opposition · USPTO

Opposition 91226134

OtherUSPTO

Opposition 91226134 at USPTO between King.com Limited and Shenzhen QiXunXinYou Technology Co., Ltd., over the mark CANDY FRENZY, filed Feb 2, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 2, 2016
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

King.com Limited

Company trademarks
Respondent

Shenzhen QiXunXinYou Technology Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the CANDY FRENZY filing.

  1. CANDY FRENZY filed

    Application 86627623 filed at the USPTO.
  2. Opposition filed

    King.com Limited started opposition 91226134 at USPTO against CANDY FRENZY.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
CANDY FRENZYContested86627623USPTO
CANDY CRUSH SAGARelied on85566839USPTO
CANDY CRUSHRelied on85840713USPTO
CANDY CRUSH SAGARelied on85966584USPTO
CANDY CRUSHRelied on85966585USPTO
CANDY TOWNRelied on86028882USPTO
CANDY FACTORYRelied on86028886USPTO
CANDY CLOUDSRelied on86028890USPTO
CANDY CRUSHERRelied on86200666USPTO
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_6b2e9d6b-9356-4728-b7ee-383ce7940056
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6b2e9d6b-9356-4728-b7ee-383ce7940056",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91226134",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-02-02",
  "parties": [
    {
      "name": "King.com Limited",
      "role": "opponent"
    },
    {
      "name": "Shenzhen QiXunXinYou Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}