Opposition 91297527
OtherUSPTO
Opposition 91297527 at USPTO between On Clouds GmbH and Myungsik Kim, over the mark EOHCLOUD, filed Mar 11, 2025. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Mar 11, 2025
- Marks involved
- 49
Parties
Who is involved
The parties as named in the office record.
Respondent
Myungsik Kim
Timeline
How the case has moved
Dates from the USPTO record and the EOHCLOUD filing.
EOHCLOUD filed
Application 98569994 filed at the USPTO.Opposition filed
On Clouds GmbH started opposition 91297527 at USPTO against EOHCLOUD.
Marks
Marks involved
1 contested mark, 48 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| EOHCLOUD | Contested | 98569994 | USPTO |
| [Design mark] | Relied on | 79139861 | USPTO |
| CLOUDSURFER | Relied on | 79169647 | USPTO |
| RUN ON CLOUDS. | Relied on | 79169648 | USPTO |
| CLOUDVENTURE | Relied on | 79189498 | USPTO |
| CLOUDFLASH | Relied on | 79199351 | USPTO |
| CLOUDFLOW | Relied on | 79199352 | USPTO |
| CLOUDRUSH | Relied on | 79208154 | USPTO |
| CLOUDFLYER | Relied on | 79211556 | USPTO |
| CLOUD X | Relied on | 79218237 | USPTO |
| CLOUDACE | Relied on | 79233628 | USPTO |
| CLOUD EDGE | Relied on | 79235691 | USPTO |
+37 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_a13a62d5-7fb9-4dd5-96bb-33efcfffef02
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_a13a62d5-7fb9-4dd5-96bb-33efcfffef02",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91297527",
"status": "other",
"office_code": "US",
"filed_date": "2025-03-11",
"parties": [
{
"name": "On Clouds GmbH",
"role": "opponent"
},
{
"name": "Myungsik Kim",
"role": "respondent"
}
]
}