Opposition 91295014
OtherUSPTO
Opposition 91295014 at USPTO between Fuente Marketing Ltd. and Fluresh LLC, over the mark MR. X, filed Nov 7, 2024. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Nov 7, 2024
- Marks involved
- 23
Parties
Who is involved
The parties as named in the office record.
Opponent
Fuente Marketing Ltd.
Timeline
How the case has moved
Dates from the USPTO record and the MR. X filing.
MR. X filed
Application 97881714 filed at the USPTO.Opposition filed
Fuente Marketing Ltd. started opposition 91295014 at USPTO against MR. X.
Marks
Marks involved
2 contested marks, 21 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| MR. X | Contested | 97881714 | USPTO |
| MR. X | Contested | 97881716 | USPTO |
| FUENTE FUENTE OPUS "X" | Relied on | 74550044 | USPTO |
| FUENTE OPUS X | Relied on | 75030336 | USPTO |
| FUENTE OPUS X FF | Relied on | 75069035 | USPTO |
| X | Relied on | 75749265 | USPTO |
| FUENTE OPUSX | Relied on | 75857912 | USPTO |
| X TO THE THIRD POWER | Relied on | 75859380 | USPTO |
| FORBIDDENX | Relied on | 75982386 | USPTO |
| X | Relied on | 76290310 | USPTO |
| X | Relied on | 77064649 | USPTO |
| X | Relied on | 78524998 | USPTO |
+11 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_3fe50f59-fba7-4add-9478-e3a9588f0f4f
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_3fe50f59-fba7-4add-9478-e3a9588f0f4f",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91295014",
"status": "other",
"office_code": "US",
"filed_date": "2024-11-07",
"parties": [
{
"name": "Fuente Marketing Ltd.",
"role": "opponent"
},
{
"name": "Fluresh LLC",
"role": "respondent"
}
]
}