Opposition · USPTO

Opposition 91244541

OtherUSPTO

Opposition 91244541 at USPTO between Vans, Inc. and Shenzhen Mandaoyuan Electronic Commerce Co., Ltd, over the mark VANSAFETY, filed Oct 31, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 31, 2018
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Vans, Inc.

Company trademarks
Respondent

Shenzhen Mandaoyuan Electronic Commerce Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the VANSAFETY filing.

  1. VANSAFETY filed

    Application 87826993 filed at the USPTO.
  2. Opposition filed

    Vans, Inc. started opposition 91244541 at USPTO against VANSAFETY.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
VANSAFETYContested87826993USPTO
VANSRelied on73396323USPTO
VANSRelied on73441417USPTO
VANSRelied on74458715USPTO
VANSRelied on74458716USPTO
VANS OFF THE WALLRelied on75229185USPTO
VANSRelied on75505409USPTO
VANSRelied on77802906USPTO
VANSRelied on77892951USPTO
VANSRelied on77892955USPTO
VAULT BY VANSRelied on78485592USPTO
VANSRelied on85585096USPTO
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_77f526ec-e940-4715-8e74-66c5b02bb044
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_77f526ec-e940-4715-8e74-66c5b02bb044",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91244541",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-10-31",
  "parties": [
    {
      "name": "Vans, Inc.",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Mandaoyuan Electronic Commerce  Co., Ltd",
      "role": "respondent"
    }
  ]
}