Opposition · USPTO

Opposition 91240655

OtherUSPTO

Opposition 91240655 at USPTO between Wright & McGill Co. and Yantai Xunmai Trading Co, Ltd, over the mark EAGLEZONE, filed Apr 4, 2018. Status in the office record: other.

View EAGLEZONEGet this data via the API
Status
Other
Result
Other
Filed
Apr 4, 2018
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Wright & McGill Co.

Company trademarks
Respondent

Yantai Xunmai Trading Co, Ltd

Timeline

How the case has moved

Dates from the USPTO record and the EAGLEZONE filing.

  1. EAGLEZONE filed

    Application 87416484 filed at the USPTO.

  2. Opposition filed

    Wright & McGill Co. started opposition 91240655 at USPTO against EAGLEZONE.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
EAGLEZONEContested87416484USPTO
EAGLE CLAW HOOKSRelied on71531071USPTO
[Design mark]Relied on71616576USPTO
EAGLE CLAWRelied on74524642USPTO
EAGLE CLAWRelied on74524643USPTO
[Design mark]Relied on74524644USPTO
[Design mark]Relied on74524646USPTO
[Design mark]Relied on74535491USPTO
EAGLE CLAWRelied on87530755USPTO
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_8414f312-2cb6-4f76-90d4-ad2fee940208
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8414f312-2cb6-4f76-90d4-ad2fee940208",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91240655",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-04-04",
  "parties": [
    {
      "name": "Wright & McGill Co.",
      "role": "opponent"
    },
    {
      "name": "Yantai Xunmai Trading Co, Ltd",
      "role": "respondent"
    }
  ]
}