Opposition · USPTO

Opposition 91243658

OtherUSPTO

Opposition 91243658 at USPTO between LVGV, LLC and M Group Hotels Inc, over the mark M HOTEL MIAMI BEACH, filed Sep 18, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 18, 2018
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

LVGV, LLC

Respondent

M Group Hotels Inc

Timeline

How the case has moved

Dates from the USPTO record and the M HOTEL MIAMI BEACH filing.

  1. M HOTEL MIAMI BEACH filed

    Application 87736870 filed at the USPTO.
  2. Opposition filed

    LVGV, LLC started opposition 91243658 at USPTO against M HOTEL MIAMI BEACH.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
M HOTEL MIAMI BEACHContested87736870USPTO
M RESORT· SPA · CASINO LAS VEGASRelied on77341800USPTO
M RESORT · SPA · CASINO LAS VEGASRelied on77341801USPTO
M RESORT · SPA · CASINO LAS VEGASRelied on77344167USPTO
M RESORT · SPA · CASINO LAS VEGASRelied on77344169USPTO
M RESORT · SPA · CASINO LAS VEGASRelied on77344171USPTO
M RESORTRelied on77864304USPTO
M RESORTRelied on77864323USPTO
MRelied on78811911USPTO
MRelied on78979735USPTO
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_902119b8-f471-4b0b-9ecd-0875b19eba81
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_902119b8-f471-4b0b-9ecd-0875b19eba81",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91243658",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-09-18",
  "parties": [
    {
      "name": "LVGV, LLC",
      "role": "opponent"
    },
    {
      "name": "M Group Hotels Inc",
      "role": "respondent"
    }
  ]
}