Opposition · USPTO

Opposition 91198528

OtherUSPTO

Opposition 91198528 at USPTO between BBY Solutions, Inc. and Buyabargain LLC AKA Buyabargain.com, over the mark BUYABARGAIN .COM, filed Feb 9, 2011. Status in the office record: other.

View BUYABARGAIN .COMGet this data via the API
Status
Other
Result
Other
Filed
Feb 9, 2011
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

BBY Solutions, Inc.

Company trademarks
Respondent

Buyabargain LLC AKA Buyabargain.com

Timeline

How the case has moved

Dates from the USPTO record and the BUYABARGAIN .COM filing.

  1. BUYABARGAIN .COM filed

    Application 77624289 filed at the USPTO.

  2. Opposition filed

    BBY Solutions, Inc. started opposition 91198528 at USPTO against BUYABARGAIN .COM.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
BUYABARGAIN .COMContested77624289USPTO
BEST BUYRelied on74013622USPTO
BEST BUYRelied on74519982USPTO
BEST BUYRelied on74680472USPTO
BEST BUY MOBILERelied on77318423USPTO
BEST BUYRelied on77559242USPTO
BEST BUYRelied on77575922USPTO
[Design mark]Relied on77586929USPTO
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_d76f1307-d52f-4913-8735-8efba1044cdd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_d76f1307-d52f-4913-8735-8efba1044cdd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91198528",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-02-09",
  "parties": [
    {
      "name": "BBY Solutions, Inc.",
      "role": "opponent"
    },
    {
      "name": "Buyabargain LLC AKA Buyabargain.com",
      "role": "respondent"
    }
  ]
}