Opposition · USPTO

Opposition 91239911

OtherUSPTO

Opposition 91239911 at USPTO between Volvo Trademark Holding AB and Shenzhen VOLO Cycling Accessories Co., Ltd, over the mark VOLO, filed Mar 7, 2018. Status in the office record: other.

View VOLOGet this data via the API
Status
Other
Result
Other
Filed
Mar 7, 2018
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Volvo Trademark Holding AB

Company trademarks
Respondent

Shenzhen VOLO Cycling Accessories Co., Ltd

Timeline

How the case has moved

Dates from the USPTO record and the VOLO filing.

  1. VOLO filed

    Application 87487808 filed at the USPTO.

  2. Opposition filed

    Volvo Trademark Holding AB started opposition 91239911 at USPTO against VOLO.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
VOLOContested87487808USPTO
VOLVORelied on71697349USPTO
VOLVORelied on72441642USPTO
VOLVORelied on73242855USPTO
VOLVORelied on73242912USPTO
VOLVORelied on73242913USPTO
VOLVORelied on73316143USPTO
VOLVORelied on73316884USPTO
VOLVORelied on78531596USPTO
VOLVORelied on78532776USPTO
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_3c7df7d3-7ed2-4294-8fea-4817eb9f6e0d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3c7df7d3-7ed2-4294-8fea-4817eb9f6e0d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91239911",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-03-07",
  "parties": [
    {
      "name": "Volvo Trademark Holding AB",
      "role": "opponent"
    },
    {
      "name": "Shenzhen VOLO Cycling Accessories Co., Ltd",
      "role": "respondent"
    }
  ]
}