Opposition · USPTO

Opposition 91307495

SuspendedUSPTO

Opposition 91307495 at USPTO between Rain Bird Corporation and Shenzhen Xmitech Electronic Co., Ltd., over the mark KOOBIRD, filed May 20, 2026. Status in the office record: suspended.

View KOOBIRDGet this data via the API
Status
Suspended
Filed
May 20, 2026
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Rain Bird Corporation

Company trademarks
Respondent

Shenzhen Xmitech Electronic Co., Ltd.

Timeline

How the case has moved

Dates from the USPTO record and the KOOBIRD filing.

  1. KOOBIRD filed

    Application 99321045 filed at the USPTO.

  2. Opposition filed

    Rain Bird Corporation started opposition 91307495 at USPTO against KOOBIRD.
  3. Next

    Suspended

    No decision is recorded at USPTO yet.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
KOOBIRDContested99321045USPTO
RAIN BIRDRelied on72177093USPTO
RAIN BIRDRelied on72429262USPTO
RAIN BIRDRelied on72429350USPTO
RAIN BIRDRelied on73776298USPTO
RAIN BIRDRelied on86543047USPTO
RAIN BIRDRelied on86543236USPTO
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_18696435-2384-439d-a35f-83a7c3ae20c6
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_18696435-2384-439d-a35f-83a7c3ae20c6",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91307495",
  "status": "suspended",
  "office_code": "US",
  "filed_date": "2026-05-20",
  "parties": [
    {
      "name": "Rain Bird Corporation",
      "role": "opponent"
    },
    {
      "name": "Shenzhen Xmitech Electronic Co., Ltd.",
      "role": "respondent"
    }
  ]
}