Opposition · USPTO

Opposition 91274180

OtherUSPTO

Opposition 91274180 at USPTO between Volkswagen Aktiengesellschaft and Shenzhen Tianfeng Technology Co., Ltd., over the mark VWRXBZ, filed Jan 26, 2022. Status in the office record: other.

View VWRXBZGet this data via the API
Status
Other
Result
Other
Filed
Jan 26, 2022
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Volkswagen Aktiengesellschaft

Respondent

Shenzhen Tianfeng Technology Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the VWRXBZ filing.

  1. VWRXBZ filed

    Application 90440576 filed at the USPTO.

  2. Opposition filed

    Volkswagen Aktiengesellschaft started opposition 91274180 at USPTO against VWRXBZ.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
VWRXBZContested90440576USPTO
VWRelied on74417830USPTO
VWRelied on75598237USPTO
VWRelied on75843232USPTO
VWRelied on75843574USPTO
VWRelied on79001131USPTO
VWRelied on79001133USPTO
VWRelied on79001521USPTO
VW AGRelied on79104474USPTO
VWOSRelied on79229601USPTO
VWRelied on79295838USPTO
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_486fbd56-ad51-46b5-bb7f-3a2c982694a8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_486fbd56-ad51-46b5-bb7f-3a2c982694a8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91274180",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-01-26",
  "parties": [
    {
      "name": "Volkswagen Aktiengesellschaft",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Tianfeng Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}