Montgomery County MD Building Energy Benchmarking Data

Montgomery County, Maryland building energy benchmarking by building and year, including county government buildings such as the Council Office Building. Records carry ENERGY STAR score and floor area next to site EUI.

Here is one real record from this actor.

{
  "buildingSignalId": "f996727a931d6b71",
  "jurisdiction": "Montgomery County, MD",
  "programName": "Montgomery County Building Energy Benchmarking",
  "country": "US",
  "reportingYear": 2024,
  "sourceRecordId": "00152444",
  "propertyName": "Council Office Building***",
  "addressStreet": "100 Maryland Ave",
  "city": "Rockville",
  "state": "MD",
  "zip": "20850",
  "propertyType": "Office",
  "propertyTypeRaw": "office",
  "grossFloorAreaSqft": 131203,
  "yearBuilt": 1952,
  "numberOfBuildings": 1,
  "energyStarScore": 32,
  "siteEuiKbtuSqft": 110.1,
  "weatherNormalizedSiteEuiKbtuSqft": 111.8,
  "sourceEuiKbtuSqft": 282.9,
  "electricityKwh": 3677655,
  "naturalGasTherms": 17970,
  "ghgEmissionsMtco2e": 1196.7,
  "ghgIntensityKgco2eSqft": 9.12,
  "complianceStatus": "compliant",
  "complianceStatusRaw": "in compliance",
  "source": "Montgomery County Energy Benchmarking",
  "benchmarkingGroup": "County",
  "portfolioManagerId": "5244852",
  "firstReportingYear": 2016,
  "observedAt": "2026-10-22T23:17:37.494Z"
}

Input | Output | Pricing

Table of contents

• What you get
• Input and filters
• Use cases
• Coverage and freshness
• Pricing
• Comparison with other Apify actors
• Related BuildingSignal actors
• FAQ
• Run it through the Apify API

What you get

Each record can carry these 31 fields. A field the source does not publish for a record comes back as null.

Field	Type	Description
buildingSignalId	string	Stable BuildingSignal building ID (same building across years and runs)
jurisdiction	string	City, county, state or province of the program
programName	string	Name of the disclosure or compliance program
country	string	Country code (US or CA)
reportingYear	number	Data year of the report
sourceRecordId	string	Building ID used by the program
propertyName	string	Property or building name
addressStreet	string	Street address
city	string	City
state	string	State or province
zip	string	ZIP or postal code
propertyType	string	Property type normalized to ENERGY STAR Portfolio Manager categories
propertyTypeRaw	string	Property type exactly as published
grossFloorAreaSqft	number	Gross floor area (sq ft)
yearBuilt	number	Year built
numberOfBuildings	number	Number of buildings on the property
energyStarScore	number	ENERGY STAR score (1-100; 50 = national median, 75+ = top performer)
siteEuiKbtuSqft	number	Site energy use intensity (kBtu per sq ft per year)
weatherNormalizedSiteEuiKbtuSqft	number	Weather-normalized site EUI (kBtu per sq ft)
sourceEuiKbtuSqft	number	Source energy use intensity (kBtu per sq ft)
electricityKwh	number	Annual grid electricity use (kWh)
naturalGasTherms	number	Annual natural gas use (therms)
ghgEmissionsMtco2e	number	Total greenhouse gas emissions (metric tons CO2e)
ghgIntensityKgco2eSqft	number	GHG emissions intensity (kg CO2e per sq ft)
complianceStatus	string	Normalized status: compliant, not_submitted, non_compliant, exempt, pending or other
complianceStatusRaw	string	Compliance/reporting status exactly as published
source	string	Official source program or agency
benchmarkingGroup	string	Benchmarking group / cohort
portfolioManagerId	string	ENERGY STAR Portfolio Manager property ID
firstReportingYear	number	First year the building was required to report
observedAt	string	When this record was collected (ISO timestamp)

Input and filters

All inputs are optional.

Field	Type	Required	Default	Description
reportingYears	array	no	(none)	Only these reporting years, e.g. 2023, 2024. Leave empty for the most recent year of every building.
latestYearOnly	boolean	no	true	Return only the most recent report of each building (ignored when reporting years are set). Turn off to get the full history.
propertyTypes	array	no	(none)	Keep only buildings whose type contains any of these words, e.g. Office, Multifamily, Hotel, Warehouse.
minFloorAreaSqft	integer	no	(none)	Only buildings at least this large.
maxFloorAreaSqft	integer	no	(none)	Only buildings up to this size.
minSiteEui	integer	no	(none)	Only buildings using at least this much energy per square foot. High EUI = retrofit opportunity.
maxSiteEui	integer	no	(none)	Only buildings using at most this much energy per square foot.
minEnergyStarScore	integer	no	(none)	Only buildings with at least this ENERGY STAR score (1-100).
maxEnergyStarScore	integer	no	(none)	Only buildings with at most this ENERGY STAR score (1-100). Low scores = inefficient buildings.
complianceStatuses	array	no	(none)	Keep only these reporting/compliance statuses. Values: compliant, not_submitted, non_compliant, exempt, pending.
zipCodes	array	no	(none)	Only buildings in these ZIP or postal codes.
ownerKeyword	string	no	(none)	Only buildings whose published owner or responsible entity contains this text (where the program publishes it).
maxBuildings	integer	no	50	Maximum number of buildings to return. Free Apify plans are limited to 10 per run.

A working example to paste into the Input tab:

{
  "maxBuildings": 25
}

Use cases

• Compare buildings in Rockville and Silver Spring by score.
• Find old low-scoring offices using yearBuilt together with energyStarScore.
• Track county building improvements over reporting years.

Coverage and freshness

Program: Montgomery County Building Energy Benchmarking. Publisher: Montgomery County Energy Benchmarking. Area in this example record: Montgomery County, MD. Each run reads the current official publication, so a scheduled run picks up new releases when the agency publishes them. Fields the program does not publish come back as null.

Pricing

This actor uses pay-per-event pricing. These are the current Apify prices, read on 2026-11-06.

Event	Price	When it is charged
result	$0.015	Each building delivered to your dataset
apify-actor-start	$0.003	When a run starts, once per GB of run memory with a minimum of one

At the default 512 MB, a run that delivers 100 buildings costs $1.503.

• Accounts on the free Apify plan receive up to 10 results per run.
• If nothing matches your filters, no results are charged. If the source cannot be read before any result is saved, you get one row with an error field, and that row carries no result charge. The start event still applies to the run.
• Set a maximum cost per run and the actor stops delivering results when it reaches that limit.

Comparison with other Apify actors

No dedicated actor for this source on the Apify Store as of November 2026. We searched the public Store on 2026-11-06 with queries including "montgomery county building energy" and "montgomery county energy benchmarking", and we reviewed the listings for this source and data type. Store listings change, so run the same search before you rely on this.

Related BuildingSignal actors

Other public BuildingSignal actors for the same buyer:

• Maryland BEPS Covered Buildings List: Energy Performance: building energy and compliance data
• US Building Energy Benchmarking Data: EUI, ENERGY STAR & GHG: building energy and compliance data
• Ann Arbor Building Energy Benchmarking Data: building energy and compliance data
• Berkeley BESO Building Energy & Compliance Data: building energy and compliance data

FAQ

What do EUI and ENERGY STAR score mean?

Site EUI is the energy a building uses per square foot per year; higher means less efficient for its type. The ENERGY STAR score (1-100) compares a building to similar buildings nationwide: 50 is the median, 75+ is top performer.

Why are some values empty?

Programs publish different fields, and buildings that did not report have no energy values. Empty values are returned as null rather than guessed.

Where does the data come from?

From official public records and open-data disclosures published by the government programs named on this page. BuildingSignal standardizes them into one consistent schema. Always confirm critical decisions with the issuing agency.

Can I use it with my CRM or BI tool?

Yes. Export to CSV, Excel or JSON, call it through the Apify API, or connect it with the Make, Zapier, n8n or Google Sheets integrations.

Run it through the Apify API

Replace <TOKEN> with your Apify API token.

curl -X POST "https://api.apify.com/v2/acts/buildingsignal~montgomery-county-building-benchmarking/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"maxBuildings": 25}'

With the Apify CLI:

$apify call buildingsignal/montgomery-county-building-benchmarking --input '{"maxBuildings": 25}'

Every run writes to a dataset that you can export as JSON, CSV or Excel from the Storage tab or through the Apify API.

---

BuildingSignal is an independent data provider and is not affiliated with, endorsed by or sponsored by any government agency or program named on this page. Data comes from official public records; always confirm critical decisions with the issuing agency.