Data Axle Historical Database
Fixed annual July point-in-time snapshots of operating business locations from 1997 through the most recently completed year, currently July 2025, with one record per operating location per snapshot and persistent `info…
Questions this answers
6 · best fit firstFor buyer-filtered annual operating-location snapshots, Data Axle supplies an estimated opened-for-business year interval, first-database-appearance year explicitly distinguished from opening, persistent location identity, snapshot year/month, industry and geography fields, and filtered frequency counts. This supports a distribution of externally observed operating-location age when the answer preserves estimate-versus-first-observation semantics, the 1997 left-censor boundary, snapshot vintage, and Data Axle classification basis; it does not establish legal formation age.
Fixed annual July snapshots, one record per included operating location, persistent location identifiers, year-specific industry/geography fields, and filtered record/frequency counts support operating-location stock levels and net changes by snapshot. Persistent IDs also let an analysis distinguish database appearances and disappearances from net stock change, but those flows must be labelled observed entry/exit rather than exact business openings or closures, and no official establishment-universe completeness is claimed.
Annual operating-location records and buyer-defined filtered counts provide reported or estimated location, parent, and corporate employee measures plus model-type indicators, alongside year-specific geography and industry. This directly supports the employment component of economic-scale distributions. Sales fields are not relied on for a currency-comparable distribution because their public currency, period, and model-version basis is unstated; payroll and receipts are not claimed.
The complete annual location snapshots provide one persistent identifier per operating location, documented parent-location linkage, physical address/geography, location-role coding, and buyer-filtered record retrieval. They support a bounded distribution of observed linked operating-location counts and geographic footprints under the documented parent-linkage rule. The claim does not equate the linkage to legal corporate control, registered addresses, or a universal firm identifier, and coded-role labels remain licence-dependent.
For a selected July snapshot and buyer-defined area, industry, and size filters, the Scan API returns matching records and Insights returns filtered counts; the product documents one record per included operating business location and marks included snapshot records in business. This directly supports the operating-location or establishment-like count component, not a legal-firm count, exhaustive employer/nonemployer universe, or official population estimate.
Persistent location identifiers across fixed annual operating-only snapshots allow a buyer to define a first-observed operating-location cohort and measure the share still observed in later July snapshots. This is supplemental evidence of database-observed location continuation, with horizons and denominators calculated from pinned snapshots; first appearance is not opening, disappearance is not an exact closure event, and firm survival, causal failure, uncensored all-market survival, and a vendor-emitted survival rate are not claimed.
Fields it delivers
18 fieldsFirst-party product documentation was checked, but whether the documented historical snapshot product covers only the United States or additional markets remains unresolved; no geography is inferred from provider location, branding, or examples.
The vendor offers this source to business buyers through sales, subscription, membership, order, or a customer-specific commercial agreement; the cited product materials do not document a sufficient free business tier. That agreement-based standing route is paid.
Want Data Axle Historical Database tested on your records?
We run match and fill rates on a sample of your data, then handle the contract, security review, and delivery into your stack if it earns its place.