Opposition · USPTO

Opposition 91225796

OtherUSPTO

Opposition 91225796 at USPTO between Kellogg North America Company and King.com Limited, over the mark ALTER-EGGO, filed Jan 12, 2016. Status in the office record: other.

Status
Other
Result
Other
Filed
Jan 12, 2016
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Kellogg North America Company

Respondent

King.com Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the ALTER-EGGO filing.

  1. ALTER-EGGO filed

    Application 86627812 filed at the USPTO.
  2. Opposition filed

    Kellogg North America Company started opposition 91225796 at USPTO against ALTER-EGGO.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
ALTER-EGGOContested86627812USPTO
EGGORelied on72068806USPTO
EGGORelied on72335443USPTO
L 'EGGO MY EGGORelied on75533599USPTO
L'EGGO MY EGGORelied on77021301USPTO
EGGORelied on77220790USPTO
EGGORelied on77882388USPTO
EGGORelied on78723394USPTO
EGGO BITESRelied on85923122USPTO
EGGO DRIZZLERSRelied on86001838USPTO
EGGORelied on86177391USPTO
EGGORelied on86426587USPTO
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_194ad89b-4943-492c-8a92-448cb6dcfc63
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_194ad89b-4943-492c-8a92-448cb6dcfc63",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91225796",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-01-12",
  "parties": [
    {
      "name": "KELLOGG NORTH AMERICA COMPANY",
      "role": "opponent"
    },
    {
      "name": "King.com Limited",
      "role": "respondent"
    }
  ]
}