Opposition 91253512
OtherUSPTO
Opposition 91253512 at USPTO between Vulcan Inc. and Kai Data, LLC, over the mark VULCAN7, filed Jan 15, 2020. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jan 15, 2020
- Marks involved
- 12
Parties
Who is involved
The parties as named in the office record.
Opponent
Vulcan Inc.
Respondent
Kai Data, LLC
Timeline
How the case has moved
Dates from the USPTO record and the VULCAN7 filing.
VULCAN7 filed
Application 88429386 filed at the USPTO.Opposition filed
Vulcan Inc. started opposition 91253512 at USPTO against VULCAN7.
Marks
Marks involved
1 contested mark, 11 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| VULCAN7 | Contested | 88429386 | USPTO |
| VULCAN | Relied on | 75675810 | USPTO |
| VULCAN | Relied on | 75675837 | USPTO |
| VULCAN | Relied on | 75675843 | USPTO |
| VULCAN | Relied on | 75677006 | USPTO |
| VULCAN | Relied on | 76291451 | USPTO |
| VULCAN REAL ESTATE | Relied on | 78875757 | USPTO |
| VULCAN REAL ESTATE | Relied on | 78875777 | USPTO |
| V VULCAN REAL ESTATE | Relied on | 78875806 | USPTO |
| VULCAN REAL ESTATE | Relied on | 78875999 | USPTO |
| V VULCAN REAL ESTATE | Relied on | 78876007 | USPTO |
| VULCAN | Relied on | 86597675 | USPTO |
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_3b709a01-de70-4d3b-8fd6-2bb3635e7306
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_3b709a01-de70-4d3b-8fd6-2bb3635e7306",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91253512",
"status": "other",
"office_code": "US",
"filed_date": "2020-01-15",
"parties": [
{
"name": "Vulcan Inc.",
"role": "opponent"
},
{
"name": "Kai Data, LLC",
"role": "respondent"
}
]
}