US6763299B2 Patent litigation record

Patent 10 cases

US6763299B2 has been asserted in 10 cases on record. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

10 cases on record

Cases on record
10
Asserted by
Shipping & Transit
Asserted against
Woodland International Transport · Does · GeoMetrix USA · Baby Supermall · Laneaxis · Fragrancenet.com · Hawk Applications · Neptune Cigars · Coastermatic · Adorama
Courts
C.D. Cal. · S.D.N.Y.
Technology
traffic control systems and business, commerce & admin data processing
Case no.PartiesCourtFiledDurationOutcome
2:16-cv-06534 Shipping & Transit, LLC v. Woodland International Transport Company, Inc. C.D. Cal. 30 Aug 2016 44 d Voluntary dismissal
1:16-cv-06694 Shipping & Transit, LLC v. Does S.D.N.Y. 25 Aug 2016 47 d Likely Settlement
2:16-cv-04861 Shipping & Transit, LLC v. GeoMetrix USA, Inc. C.D. Cal. 1 Jul 2016 104 d Voluntary dismissal
2:16-cv-03947 Shipping & Transit, LLC v. Baby Supermall, LLC C.D. Cal. 6 Jun 2016 43 d Voluntary dismissal
2:16-cv-03953 Shipping & Transit, LLC v. Laneaxis, Inc. C.D. Cal. 6 Jun 2016 113 d Likely Settlement
2:16-cv-03981 Shipping & Transit, LLC v. Fragrancenet.com, Inc. C.D. Cal. 6 Jun 2016 25 d Voluntary dismissal
2:16-cv-03982 Shipping & Transit, LLC v. Hawk Applications, Corp. C.D. Cal. 6 Jun 2016 113 d Likely Settlement
2:16-cv-03836 Shipping & Transit, LLC v. Neptune Cigars, Inc. C.D. Cal. 1 Jun 2016 104 d Judgment on the Merits
2:16-cv-02226 Shipping & Transit, LLC v. Coastermatic, Inc. C.D. Cal. 31 Mar 2016 88 d Voluntary dismissal
2:16-cv-02149 Shipping & Transit, LLC v. Adorama, Inc. C.D. Cal. 29 Mar 2016 147 d Case Transferred
Source: Patsnap Litigation Data. Cases asserting US6763299B2 in the current snapshot. Run this in Eureka
Patsnap Eureka

How strong is US6763299B2?

Closest prior art, compared claim by claim, with every reference rated for how hard it hits.

Run a novelty search
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.