Opposition · USPTO

Opposition 91244336

OtherUSPTO

Opposition 91244336 at USPTO between Zynga Inc. and C Beaumont LLC, over the mark VEGASVILLE, filed Oct 23, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 23, 2018
Marks involved
36
Parties

Who is involved

The parties as named in the office record.

Opponent

Zynga Inc.

Company trademarks
Respondent

C Beaumont LLC

Timeline

How the case has moved

Dates from the USPTO record and the VEGASVILLE filing.

  1. VEGASVILLE filed

    Application 87561320 filed at the USPTO.
  2. Opposition filed

    Zynga Inc. started opposition 91244336 at USPTO against VEGASVILLE.
Marks

Marks involved

1 contested mark, 35 marks the challenger relies on.

MarkRoleApplicationOffice
VEGASVILLEContested87561320USPTO
FARMVILLE BY ZYNGARelied on77798840USPTO
FARMVILLERelied on77804837USPTO
CITYVILLERelied on77920777USPTO
FARMVILLERelied on77969341USPTO
FARMVILLERelied on77980346USPTO
FRONTIERVILLERelied on77983529USPTO
CITYVILLERelied on85187572USPTO
FRONTIERVILLERelied on85187815USPTO
FARMVILLERelied on85187825USPTO
REWARDVILLERelied on85283115USPTO
FARMVILLE ENGLISH COUNTRYSIDERelied on85290860USPTO

+24 more marks in this case

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_31702411-3623-4c8b-a86b-fcb0b18d7d23
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_31702411-3623-4c8b-a86b-fcb0b18d7d23",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91244336",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-10-23",
  "parties": [
    {
      "name": "Zynga Inc.",
      "role": "opponent"
    },
    {
      "name": "C Beaumont LLC",
      "role": "respondent"
    }
  ]
}