Opposition · USPTO

Opposition 91297440

OtherUSPTO

Opposition 91297440 at USPTO between MVW Holdings, Inc. and Smart Subscriptions LLC, over the mark MAGNEWORLD, filed Mar 6, 2025. Status in the office record: other.

View MAGNEWORLDGet this data via the API
Status
Other
Result
Other
Filed
Mar 6, 2025
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

MVW Holdings, Inc.

Company trademarks
Respondent

Smart Subscriptions LLC

Timeline

How the case has moved

Dates from the USPTO record and the MAGNEWORLD filing.

  1. MAGNEWORLD filed

    Application 98635642 filed at the USPTO.

  2. Opposition filed

    MVW Holdings, Inc. started opposition 91297440 at USPTO against MAGNEWORLD.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
MAGNEWORLDContested98635642USPTO
MAGNA-TILESRelied on76368521USPTO
MAGNA-QUBIXRelied on87729304USPTO
MAGNA-TILESRelied on87887751USPTO
MAGNA-TILESRelied on88800238USPTO
MAGNA-TILESRelied on88800246USPTO
MAGNA-TILESRelied on97906449USPTO
THE ORIGINAL MAGNA-TILESRelied on98452089USPTO
THE ORIGINAL MAGNA-TILESRelied on98826855USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_994e9f34-7a7b-4f5d-bb13-31151f158684
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_994e9f34-7a7b-4f5d-bb13-31151f158684",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91297440",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-03-06",
  "parties": [
    {
      "name": "MVW Holdings, Inc.",
      "role": "opponent"
    },
    {
      "name": "Smart Subscriptions LLC",
      "role": "respondent"
    }
  ]
}