Opposition 91304263
OtherUSPTO
Opposition 91304263 at USPTO between TE Connectivity Solutions GmbH and Yong Fu, over the mark AMPCUBFOX, filed Jan 6, 2026. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jan 6, 2026
- Marks involved
- 25
Parties
Who is involved
The parties as named in the office record.
Respondent
Yong Fu
Timeline
How the case has moved
Dates from the USPTO record and the AMPCUBFOX filing.
AMPCUBFOX filed
Application 99067866 filed at the USPTO.Opposition filed
TE Connectivity Solutions GmbH started opposition 91304263 at USPTO against AMPCUBFOX.
Marks
Marks involved
1 contested mark, 24 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| AMPCUBFOX | Contested | 99067866 | USPTO |
| AMP | Relied on | 71616197 | USPTO |
| AMPSEAL | Relied on | 72018395 | USPTO |
| AMPOWER | Relied on | 72030631 | USPTO |
| AMPLIVAR | Relied on | 72030632 | USPTO |
| AMP EDGE | Relied on | 72083422 | USPTO |
| AMP-BLADE | Relied on | 72117425 | USPTO |
| AMP-LEAF | Relied on | 72118030 | USPTO |
| AMPACT | Relied on | 72158896 | USPTO |
| AMP-TAB | Relied on | 72177326 | USPTO |
| AMPACT | Relied on | 72195265 | USPTO |
| AMPMODU | Relied on | 72210633 | USPTO |
+13 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_ace72314-5c84-406c-a37a-01fff856a5f1
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_ace72314-5c84-406c-a37a-01fff856a5f1",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91304263",
"status": "other",
"office_code": "US",
"filed_date": "2026-01-06",
"parties": [
{
"name": "TE Connectivity Solutions GmbH",
"role": "opponent"
},
{
"name": "Yong Fu",
"role": "respondent"
}
]
}