Cancellation · USPTO

Cancellation 92061241

OtherUSPTO

Cancellation 92061241 at USPTO between Wenger, S.A. and Swiss Brand Limited Inc., over the mark SWISSBRAND, filed Apr 10, 2015. Status in the office record: other.

View SWISSBRANDGet this data via the API
Status
Other
Result
Other
Filed
Apr 10, 2015
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Petitioner

Wenger, S.A.

Company trademarks
Respondent

Swiss Brand Limited Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SWISSBRAND filing.

  1. SWISSBRAND filed

    Application 85081005 filed at the USPTO.

  2. SWISSBRAND registered

  3. Cancellation filed

    Wenger, S.A. started cancellation 92061241 at USPTO against SWISSBRAND.
Marks

Marks involved

2 contested marks, 6 marks the challenger relies on.

MarkRoleApplicationOffice
SWISSBRANDContested85081005USPTO
[Design mark]Contested85674348USPTO
SWISS GEAR BY WENGERRelied on76448332USPTO
SWISSGEARRelied on76470860USPTO
[Design mark]Relied on77547582USPTO
[Design mark]Relied on77547609USPTO
[Design mark]Relied on77547618USPTO
[Design mark]Relied on77547635USPTO
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_aeb2df7b-8cad-42aa-961c-f1a35263f107
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_aeb2df7b-8cad-42aa-961c-f1a35263f107",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92061241",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-04-10",
  "parties": [
    {
      "name": "Wenger, S.A.",
      "role": "petitioner"
    },
    {
      "name": "Swiss Brand Limited Inc.",
      "role": "respondent"
    }
  ]
}