Webomates Inc.
Held is read from USPTO's recorded assignments; a transfer never recorded there does not appear.
0
Ending by 2030
Oct 2036
Next term end
When these terms end
Held patents by the year their term ends
20262027202820292030203120322033203420352036203720382039204020412042204320442045
Fee deadlines
Maintenance fees fall due 3.5, 7.5 and 11.5 years after grant. A missed fee ends a patent at the end of the six month grace period that follows, not on the due date.
- 1 fee due Dec 20, 2026The maintenance fee for Identifying feature modification in software builds using baseline data (US 11,681,609) comes due Dec 20, 2026. Unpaid by Jun 21, 2027, it lapses early.
- 1 fee due Mar 24, 2027The maintenance fee for Method and system for real-time identification of anomalous behavior in a software program (US 10,423,520) comes due Mar 24, 2027. Unpaid by Sep 24, 2027, it lapses early.
- 1 fee due Jul 28, 2027The maintenance fee for Method and system for multi-channel testing (US 10,545,859) comes due Jul 28, 2027. Unpaid by Jan 28, 2028, it lapses early.
Recent changes
Nothing was recorded against this company's patents in the last 90 days.
Patents held now
Soonest term end first. Each date below is computed on that patent's own page, which shows the rule, the adjustments and the fee history it was derived from.
Showing 1 to 9 of 9
| Patent | Title | Status | Expires | Confidence |
|---|---|---|---|---|
| US 10,175,657 | Method and system for determining mapping of test case(s) to code snippets of computer program In force · From the USPTO record | In force | From the USPTO record | |
| US 10,423,520 | Method and system for real-time identification of anomalous behavior in a software program In force · From the USPTO record | In force | From the USPTO record | |
| US 10,545,859 | Method and system for multi-channel testing In force · From the USPTO record | In force | From the USPTO record | |
| US 10,831,640 | Method and system for testing an application using multiple test case execution channels In force · From the USPTO record | In force | From the USPTO record | |
| US 11,068,387 | Classifying a test case executed on a software In force · From the USPTO record | In force | From the USPTO record | |
| US 11,249,890 | Software defect creation In force · From the USPTO record | In force | From the USPTO record | |
| US 11,550,703 | Test package analyzer In force · From the USPTO record | In force | From the USPTO record | |
| US 11,681,609 | Identifying feature modification in software builds using baseline data In force · From the USPTO record | In force | From the USPTO record | |
| US 12,360,882 | Creating an optimal test suite In force · From the USPTO record | In force | From the USPTO record |
Sources and methods
Compiled from the USPTO record, grants, published applications and recorded assignments, not yet reviewed by hand.
How this record was built
Computed patent terms end on the dates shown. Related patents and pending applications may cover overlapping subject matter.
Published applications
Every application published under this name has become a patent.