Opposition 91244269
OtherUSPTO
Opposition 91244269 at USPTO between Deutsche Telekom AG and Telogiks, LP, over the mark JUXTO JUXTO, filed Oct 19, 2018. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Oct 19, 2018
- Marks involved
- 16
Parties
Who is involved
The parties as named in the office record.
Timeline
How the case has moved
Dates from the USPTO record and the JUXTO JUXTO filing.
JUXTO JUXTO filed
Application 87696859 filed at the USPTO.Opposition filed
Deutsche Telekom AG started opposition 91244269 at USPTO against JUXTO JUXTO.
Marks
Marks involved
1 contested mark, 15 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| JUXTO JUXTO | Contested | 87696859 | USPTO |
| T | Relied on | 77307271 | USPTO |
| T MOBILE | Relied on | 77311132 | USPTO |
| T-SYSTEMS | Relied on | 77311520 | USPTO |
| T SYSTEMS | Relied on | 77364393 | USPTO |
| T | Relied on | 77364668 | USPTO |
| T MOBILE | Relied on | 77369466 | USPTO |
| [Design mark] | Relied on | 78798405 | USPTO |
| [Design mark] | Relied on | 78798428 | USPTO |
| BUSINESS MARKETPLACE T | Relied on | 79135062 | USPTO |
| HOTSPOT T MOBILE | Relied on | 79141263 | USPTO |
| HOTSPOT T | Relied on | 79141464 | USPTO |
+4 more marks in this case
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_b3da0827-25c2-4414-89b1-f3ef6cd6a033
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_b3da0827-25c2-4414-89b1-f3ef6cd6a033",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91244269",
"status": "other",
"office_code": "US",
"filed_date": "2018-10-19",
"parties": [
{
"name": "Deutsche Telekom AG",
"role": "opponent"
},
{
"name": "Telogiks, LP",
"role": "respondent"
}
]
}