Trademark Opposition Deadline USPTO Parser
3.00 in statutory 30-day TTAB trademark opposition deadlines parsed and docketed across across 3 items.
Published 2026-05-05. Statutory 30-day opposition deadline expires 2026-06-04. Immediate TTAB extension required under 37 CFR 2.101.
Method1Parsed USPTO Official Gazette publication dates and applied 37 CFR 2.101 calendar calculation logic.
2Generated automated calendar feeds (.ics) and TTAB ESTTA extension of time electronic payloads.
| Reference | Description | Critical_Deadlines |
|---|---|---|
| SN-9788102 | Statutory Opposition Deadline (BASELOOM_ENTERPRISE) | 1.00 |
| SN-9788145 | Statutory Opposition Deadline (LOOM_LOGISTICS_AI) | 1.00 |
| SN-9789402 | Statutory Opposition Deadline (LOOMWEAVE_FINANCE) | 1.00 |
USPTO Official Gazette electronic XML/HTML trademark publication feeds, plus brand trademark watch conflict criteria
TTAB opposition calendar payload (.ics/CSV) and automated Extension of Time filing manifest (Resolution Dossier, Findings Schedule)
Open Trademark Opposition Deadline USPTO Parser on sample data now with no sign-up, then run your own files free for 14 days. $2,500 a month after that, cancel any time. 30% goes to the referring partner.
Read in memory for the session, never stored, never used to train a model.
Outputs are computed from your inputs and the tool's rules. Check them before you rely on them.
14 days on your own files, then $2,500 a month.
Open Trademark Opposition Deadline USPTO Parser on sample data now with no sign-up, then run your own files free for 14 days. $2,500 a month after that, cancel any time.
On a sample file: 3.00 in statutory 30-day TTAB trademark opposition deadlines parsed and docketed across across 3 items.
Why not just use ChatGPT?
Rules that stay current: the rate cards, tariffs, code sets and regulations it checks against are kept up to date for you; a one-off prompt starts from nothing each time. Evidence that stands up: every finding cites the line, the file and the rule, so it holds up with a vendor, a payer or an auditor. The same answer every time: the checks are written rules, not a fresh guess, so this month's result can be compared with last month's. Nobody has to own it: no one inside has to build, test and maintain a home-made tool, and files are not pasted into a public chatbot.
Start on your own files
If you would rather talk it through, write to dev.sathya@baseloom.app; that reaches Dev Sathya, founder.