Cancellation · USPTO

Cancellation 92088157

OtherUSPTO

Cancellation 92088157 at USPTO between MVW Holdings, Inc. and Spinballs, LLC, over the mark MAGNABOX, filed Apr 22, 2025. Status in the office record: other.

View MAGNABOXGet this data via the API
Status
Other
Result
Other
Filed
Apr 22, 2025
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Petitioner

MVW Holdings, Inc.

Company trademarks
Respondent

Spinballs, LLC

Timeline

How the case has moved

Dates from the USPTO record and the MAGNABOX filing.

  1. MAGNABOX filed

    Application 88592250 filed at the USPTO.

  2. MAGNABOX registered

  3. Cancellation filed

    MVW Holdings, Inc. started cancellation 92088157 at USPTO against MAGNABOX.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
MAGNABOXContested88592250USPTO
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_0dd69b51-c006-42d8-a3aa-51b82d0336e8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0dd69b51-c006-42d8-a3aa-51b82d0336e8",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92088157",
  "status": "other",
  "office_code": "US",
  "filed_date": "2025-04-22",
  "parties": [
    {
      "name": "MVW Holdings, Inc.",
      "role": "petitioner"
    },
    {
      "name": "Spinballs, LLC",
      "role": "respondent"
    }
  ]
}