Opposition · USPTO

Opposition 91236796

OtherUSPTO

Opposition 91236796 at USPTO between Swatch AG (Swatch SA) (Swatch Ltd.) and Shenzhen UWatch Technology Co., Ltd., over the mark UWATCH, filed Sep 21, 2017. Status in the office record: other.

View UWATCHGet this data via the API
Status
Other
Result
Other
Filed
Sep 21, 2017
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Swatch AG (Swatch SA) (Swatch Ltd.)

Company trademarks
Respondent

Shenzhen UWatch Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the UWATCH filing.

  1. UWATCH filed

    Application 87201633 filed at the USPTO.

  2. Opposition filed

    Swatch AG (Swatch SA) (Swatch Ltd.) started opposition 91236796 at USPTO against UWATCH.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
UWATCHContested87201633USPTO
SWATCHRelied on73506848USPTO
SWATCHRelied on74079220USPTO
SWATCHRelied on74801004USPTO
SWATCHRelied on78124477USPTO
ISWATCHRelied on79053142USPTO
ESWATCHRelied on79053143USPTO
SWATCH THE EYESRelied on86722611USPTO
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_d261a8a5-f18d-45b4-a2fa-dd368f8ff7f8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d261a8a5-f18d-45b4-a2fa-dd368f8ff7f8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91236796",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-09-21",
  "parties": [
    {
      "name": "Swatch AG (Swatch SA) (Swatch Ltd.)",
      "role": "opponent"
    },
    {
      "name": "Shenzhen UWatch Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}