Opposition · USPTO

Opposition 91233501

OtherUSPTO

Opposition 91233501 at USPTO between TESSCO Corporation Incorporated and Tesco Corporation, over the mark TESCOMATION, filed Mar 21, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 21, 2017
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

TESSCO Corporation Incorporated

Respondent

Tesco Corporation

Timeline

How the case has moved

Dates from the USPTO record and the TESCOMATION filing.

  1. TESCOMATION filed

    Application 86944423 filed at the USPTO.
  2. Opposition filed

    TESSCO Corporation Incorporated started opposition 91233501 at USPTO against TESCOMATION.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
TESCOMATIONContested86944423USPTO
TESSCORelied on74127417USPTO
TESSCO TECHNOLOGIESRelied on74254117USPTO
TESSCO.COMRelied on75828363USPTO
TESSCORelied on76063991USPTO
TESSCORelied on76096752USPTO
TESSCO CONNECTRelied on86047572USPTO
TESSCO SOLUTION ARCHITECTURERelied on86512226USPTO
TESSCO FLEET VISIBILITYRelied on86801969USPTO
TESSCO FLEET MOBILITYRelied on86802016USPTO
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_e365b8fa-dad0-4994-a0d7-62f8f1bb9104
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e365b8fa-dad0-4994-a0d7-62f8f1bb9104",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91233501",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-03-21",
  "parties": [
    {
      "name": "TESSCO Corporation Incorporated",
      "role": "opponent"
    },
    {
      "name": "Tesco Corporation",
      "role": "respondent"
    }
  ]
}