Opposition · USPTO

Opposition 91245482

OtherUSPTO

Opposition 91245482 at USPTO between Deutsche Telekom AG and T-Eagle Electronic Trading Ltd., over the mark T-EAGLE, filed Dec 12, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 12, 2018
Marks involved
40
Parties

Who is involved

The parties as named in the office record.

Opponent

Deutsche Telekom AG

Company trademarks
Respondent

T-Eagle Electronic Trading Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the T-EAGLE filing.

  1. T-EAGLE filed

    Application 87686884 filed at the USPTO.
  2. Opposition filed

    Deutsche Telekom AG started opposition 91245482 at USPTO against T-EAGLE.
Marks

Marks involved

1 contested mark, 39 marks the challenger relies on.

MarkRoleApplicationOffice
T-EAGLEContested87686884USPTO
TRelied on74720652USPTO
TRelied on74720656USPTO
T-MOBILERelied on75093051USPTO
T-SYSTEMRelied on75093059USPTO
T MOBILERelied on75095186USPTO
T-MOBILERelied on75248963USPTO
T-MOBILERelied on75248964USPTO
T-SYSTEMSRelied on76166309USPTO
TRelied on76252927USPTO
T-MOBILE USARelied on76350166USPTO
TRelied on77307271USPTO

+28 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 /v1/proceedings/{id}
ID=prc_54ba5a72-7cb7-4767-b55c-868d70575669
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_54ba5a72-7cb7-4767-b55c-868d70575669",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91245482",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-12-12",
  "parties": [
    {
      "name": "Deutsche Telekom AG",
      "role": "opponent"
    },
    {
      "name": "T-Eagle Electronic Trading Ltd.",
      "role": "respondent"
    }
  ]
}