MD PG County Tax-Sale Foreclosures avatar

MD PG County Tax-Sale Foreclosures

Pricing

from $0.03 / 1,000 foreclosure records

Go to Apify Store
MD PG County Tax-Sale Foreclosures

MD PG County Tax-Sale Foreclosures

Prince George's County, MD tax-sale foreclosure register (~78.7k, 2009-present, open data): every property submitted for county tax sale - tax account, property id, submission date, address, occupied flag. Distressed-property diligence: an address's full history or a fresh-submission sweep.

Pricing

from $0.03 / 1,000 foreclosure records

Rating

0.0

(0)

Developer

Wenhao Yang

Wenhao Yang

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 hours ago

Last modified

Categories

Share

Prince George's County (MD) Tax-Sale Foreclosures

The county's property foreclosure register - every property Prince George's County has submitted for tax sale, 2009 to the present, in one queryable dataset. Distressed-property diligence: the full tax-sale history of one address, or a sweep of what's fresh across a city.

Data

Prince George's County, Maryland open data (public tax-sale register). ~78,700 properties, 2009-present - each a single submission of a delinquent-tax property to the county's tax sale.

Each record carries:

  • Tax account number - the county's tax key for the property (e.g. 17060464123)
  • County property id - the county's internal property identifier
  • Submission date - when the property was submitted for tax sale
  • Street address, city, ZIP, location - the full property address
  • Occupied flag - whether the address was occupied at submission (YES / NO)
  • Property description - a short line where the county records one

A note on the register's rhythm, stated plainly: tax-sale submissions arrive in seasonal batches, not as a steady stream - the most recent submissions in the register are from July 2026, and a county typically processes them in annual cycles. This is the deep history of which properties have been through the county's tax-sale process, ideal for property history and sweeps - not a daily feed of fresh notices.

Low cost

From $0.00005 per record, down to $0.00003 at Gold

County tax-sale data is published as a flat table where only a fraction of rows carry a real occupancy flag and submissions cluster into batches - fine for browsing the county's portal, painful if you want to actually cut it by place, status or date. We made the register directly queryable: taxAccountNumber / propertyId / address / city / zip / occupied / submission-date windows all filter before a record returns, and groupBy (counts by city / zip / occupancy / submission year) comes back as clean server counts. You query a foreclosure register that behaves like a database; the cleanup stays on our side.

Every record is one flat JSON object - no PDFs, no portal pagination.

Use cases

  • Property history - every time a given property or address went through the county's tax-sale process, with its tax account and submission date
  • Distressed-property diligence - confirm whether a property has been submitted for tax sale, when, and in which city
  • Market sweeps - aggregate submissions by city or year to see the shape of tax-sale activity across the county

Inputs

FieldWhat it does
taxAccountNumberexact county tax account lookup
propertyIdcounty property identifier
address / city / zipfind by place
occupiedYES / NO (only ~4% of properties carry a real flag)
submittedFrom / submittedTosubmission-date window
recentDayssubmissions in the last N days (batches may return little)
aggregate + groupBycounts by city / zip / occupancy / submission year

Example inputs

One property by its tax account - taxAccountNumber is exact.

{ "taxAccountNumber": "477067" }

Every submission on a street - address is a substring match.

{ "address": "Canterbury", "maxResults": 10 }

A city's submissions in a window - city with a submission-date window.

{ "city": "Bowie", "submittedFrom": "2026-01-01", "maxResults": 10 }

The county by city - one count per group.

{ "aggregate": true, "groupBy": "city" }

Output fields

submittedDate / taxAccountNumber / propertyId / address / city / zip / occupied / propertyDescription / location.

Honesty note: the county records a real occupied / vacant flag (YES / NO) on only ~4% of properties - the remaining ~96% are published as Unavailable. The occupied field is returned exactly as the county published it, never filled in. propertyId is the county's internal id, not a stable key across years.

Example output

One property - taxAccountNumber=477067 returns that property's submission; each is a record like this one. Every record also carries platform, source, and the aggregate columns groupKey / groupCount / groupBy, which are "" outside aggregate mode:

{
"platform": "md-pg-foreclosures",
"source": "pg-foreclosures",
"groupKey": "", "groupCount": "", "groupBy": "",
"taxAccountNumber": "477067",
"propertyId": "18823",
"submittedDate": "2026-07-28",
"address": "4111 Canterbury WAY",
"city": "Temple Hills",
"zip": "20748",
"occupied": "Unavailable",
"propertyDescription": "Unavailable",
"location": "4111 Canterbury WAY Temple Hills MD,20748"
}

Source: Prince George's County open data (tax-sale foreclosure register, public records).