Opposition · USPTO

Opposition 91301596

OtherUSPTO

Opposition 91301596 at USPTO between Volvo Trademark Holding AB and Shenzhen Kexun Innovation Technology Co., Ltd., over the mark VOVOZANIUM, filed Sep 10, 2025. Status in the office record: other.

View VOVOZANIUMGet this data via the API
Status
Other
Result
Other
Filed
Sep 10, 2025
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Volvo Trademark Holding AB

Company trademarks
Respondent

Shenzhen Kexun Innovation Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the VOVOZANIUM filing.

  1. VOVOZANIUM filed

    Application 98768926 filed at the USPTO.

  2. Opposition filed

    Volvo Trademark Holding AB started opposition 91301596 at USPTO against VOVOZANIUM.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
VOVOZANIUMContested98768926USPTO
VOLVORelied on71697348USPTO
VOLVORelied on71697349USPTO
VOLVORelied on73316143USPTO
VOLVORelied on73316884USPTO
VOLVORelied on76143318USPTO
VOLVORelied on76975478USPTO
VOLVORelied on78531596USPTO
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_d549e9b9-1147-4351-bb0a-e758c9e5dbe1
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d549e9b9-1147-4351-bb0a-e758c9e5dbe1",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91301596",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-09-10",
  "parties": [
    {
      "name": "Volvo Trademark Holding AB",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Kexun Innovation Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}