OR UCC Secured Parties - Lien Holder Search

When a lender takes a security interest in a business - equipment financing, inventory, receivables - it files a UCC financing statement with the Oregon Secretary of State. Those filings are public, and they are published as open data. This actor turns that register into a charged-per-record search, filter and aggregate tool: find everything a given lender has filed, pull the parties on a single statement, filter by lien type or date window, or aggregate the register.

Built for: lenders and credit analysts checking who else has a claim on a debtor, M&A and asset-based diligence, judgment and tax-lien recovery work, and anyone who wants the public record of a lien holder in Oregon without paging a state portal one name at a time.

What it covers

220,136 secured-party records - the state's current UCC register, across 214,875 filings (a statement names as many parties as it likes - one filing in this corpus carries 17 separate secured-party rows - so one filing number can return more than one row).

Each record carries:

• the secured party - the lender, lessor, trustee or tax authority holding the claim, with its street, city, state, postal code and country
• the lien type - UCC (194,722), EFS farm-products (7,604), IRS (7,323), CW construction (5,076), RW (2,477), TU transmitting utility (1,360), PF public finance (850), IRS-X released (603), ASL (97), APL (24) - each with a plain-English label alongside the source code
• the filing date and the lapse date
• a link to the filing image on the Secretary of State's record viewer

The fine print that matters

This table is the secured-party side only - it carries no debtor name or debtor address. It answers "who holds the claim", not "who owes it". (For the debtor side, see the Connecticut UCC actor, which is the mirror image.)

A filing number is not a party. The number identifies the statement; the register lists every secured party named on it, so a filing number can legitimately return more than one record - and the rows are genuinely different parties, not duplicates, so nothing is merged away. Numbers come in two shapes: a bare 8-digit form, and a suffixed form (-1, -2, -3) for the Nth party on the same statement.

Two date notes that will otherwise mislead you. 1,285 records carry no lapse date - filings with no lapse date of record - so a lapse-window query matches only filings that actually carry a date in that window; those rows are not dropped from an unfiltered pull. And 76 records carry a lapse date past 2100 (out to 2109, with one at 3030). Those are real, not junk: 75 are transmitting-utility filings, held by Wilmington Trust National Association (19), UBS AG Stamford Branch (7), Wilmington Savings Fund Society (6) and similar collateral agents, which run on long or indefinite terms. They are served exactly as the state publishes them, and because a lapse filter is bounded to plausible dates they surface on an unfiltered or near-term pull rather than through a year range.

The register is a historical archive reaching back to 1963, refreshed monthly.

Typical questions

• "Everything a given lender holds a secured claim on in Oregon."
• "IRS or construction liens by a given filer."
• "The parties on one financing statement."
• "Filings about to lapse - the liens expiring in a window."
• "Aggregate the register by lien type, state or country."

Inputs

Input	What it does
mode	rows (default) / aggregate
securedParty	lien-holder name substring
fileNumber	exact filing number (bare or suffixed form)
lienType	UCC / EFS / IRS / CW / RW / TU / PF / IRS-X / ASL / APL
city / state / country	secured-party location
filedFrom / filedTo	filing-date window
lapseFrom / lapseTo	lapse-date window
groupBy	aggregate over lien type / state / country
maxResults	cap records (default 50)

Default run = the 50 most recent secured-party records - fast for the daily auto-test. For a targeted query add a filter; for a broad view use aggregate.

Low cost

From $0.00006 per record Pay-per-event: you are charged per record delivered, and nothing for the query. Cost scales with what you pull, not with the size of the register, and each record is metered individually - a full lender pull costs a fraction of a cent.