Opposition 91304799
OtherUSPTO
Opposition 91304799 at USPTO between Riot Games, Inc. and Tang Xilin, over the mark [Design Mark], filed Jan 28, 2026. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jan 28, 2026
- Marks involved
- 12
Parties
Who is involved
The parties as named in the office record.
Respondent
Tang Xilin
Timeline
How the case has moved
Dates from the USPTO record and the [Design Mark] filing.
[Design Mark] filed
Application 99159895 filed at the USPTO.Opposition filed
Riot Games, Inc. started opposition 91304799 at USPTO against [Design Mark].
Marks
Marks involved
1 contested mark, 11 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| [Design mark] | Contested | 99159895 | USPTO |
| RIOT GAMES | Relied on | 88387301 | USPTO |
| RIOT GAMES | Relied on | 88387305 | USPTO |
| RIOT GAMES | Relied on | 88387308 | USPTO |
| RIOT GAMES | Relied on | 88387310 | USPTO |
| RIOT GAMES | Relied on | 88387312 | USPTO |
| RIOT GAMES | Relied on | 88387315 | USPTO |
| RIOT TABLETOP | Relied on | 88577439 | USPTO |
| RIOT GAMES | Relied on | 88981578 | USPTO |
| RIOT GAMES | Relied on | 88981579 | USPTO |
| RIOT GAMES | Relied on | 88981621 | USPTO |
| [Design mark] | Relied on | 99149224 | 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_64fe4ebb-c974-406e-9c6a-f6e28d4012bd
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_64fe4ebb-c974-406e-9c6a-f6e28d4012bd",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91304799",
"status": "other",
"office_code": "US",
"filed_date": "2026-01-28",
"parties": [
{
"name": "Riot Games, Inc.",
"role": "opponent"
},
{
"name": "Tang Xilin",
"role": "respondent"
}
]
}