Skip to main content

Statistikkbank — Bostøtte

Husbanken logo
StableNLODPowers 2 viewsNo fixed time range· annual

Statistikkbank — Bostøtte

Husbanken · husbanken-bostotte

Husbanken publishes bostøtte (housing allowance) application counts, decision counts, payout counts, rejection counts and the paid-out kroner amount, per kommune, per year, through its public "Statistikkbank" Qlik Sense app. Atlas reaches this over the Qlik Engine API (WebSocket JSON-RPC 2.0, officially documented by Qlik), not Power BI as an earlier investigation assumed — see atlas-data/ingest/src/sources/husbanken-bostotte/README.md for the full mechanism, including why a single-page hypercube fetch fails and the paginated fetch this source uses instead.

Provenance​

PublisherHusbanken
Upstream IDee185fe5-e94d-463e-bff8-cd1c5f2f566f
LicenseNLOD
PeriodicityP1Y
EU Data ThemeSOCI
AttributionKilde: Husbanken, Statistikkbank
Methodology
Real data coverage starts in 2010 (2008/2009 are genuinely zero, not missing) and extends through the current year (in progress). Husbanken's "Boligsosial Monitor" app on the same Qlik backend carries related but distinct indicators and is deferred — see PLAN-011 for why.

Used in Atlas views​

These Atlas views (api_v1.* PostgREST endpoints) include this dataset in their input. Click through for the sample query, column list, and lineage.

Joined with​

Datasets that co-occur with this one inside Atlas's dbt models — the datasets you'd typically combine with this one in a real query.

Dimensions​

CodeMeaningValue formatNotes
region_codeKommune code, read directly from the hypercube's `KommuneNr` dimension4-digit code (SSB standard) — not always a real kommune⚠️ Confirmed live 2026-10-02, matching the exact lesson udir-gsi learned: Svalbard's two pseudo-codes (`2100`, `2111`) are present among Husbanken's 883 distinct `KommuneNr` values, always carrying real zero values for every measure (not suppressed — Husbanken's bostøtte programme genuinely administers no Svalbard cases). Named `region_code`, not `kommune_nr`, for this reason; `kommune_nr` resolution happens downstream via this project's existing `classify_region_code`/`region_code_to_kommune_nr` dbt macros. ⚠️ Also confirmed live: `KommuneNr` carries Oslo's 15 bydeler (plus one discontinued pre-2004 one) as 4-digit codes `0311`-`0326`, named via Husbanken's own Qlik app (e.g. `0311` = "Gamle Oslo"). This is a second, incompatible bydel numbering from the 6-digit convention FHI's sources use for the same districts — `classify_region_code` now recognises both.
yearCalendar year, read from the hypercube's `År` dimension4-digit year⚠️ Confirmed live: the underlying source records at DAILY grain (31 distinct `Dato` values checked for a single January) — an earlier investigation wrongly assumed annual grain. Atlas publishes at annual grain as its own choice (matching this source's sibling indicators and PLAN-011's recommendation), not because the source is coarser than that. ⚠️ Also confirmed live: a real null-year bucket exists in Husbanken's own data (`År` as the literal text `-`), seen both nationally and per-kommune (e.g. Svalbard code 2111). These rows are dropped during parsing, not fabricated into a fake year — see parse.ts.
measureWhich bostøtte figure this row's value is — not a format variantsoknad | vedtak | utbetaling | avslag | belopFive measures: application count, decision count, payout count, rejection count, and the paid kroner amount. Named via explicit `qLabel`s set on the Qlik request (`soknad`/`vedtak`/ `utbetaling`/`avslag`/`belop`) — without a `qLabel`, Qlik echoes the raw expression string (e.g. `Sum(BostøtteSøknadTeller)`) instead, confirmed live.
valueThe measure's numeric value for this kommune and yearInteger count, or kroner for the `belop` measure; no suppression marker foundChecked live against Røyrvik (kommune 5043, Norway's smallest by bostøtte volume) — every cell is a real number, not a suppression placeholder. No suppression convention was found anywhere in this dataset during Phase 1/2 research.

Sample query​

Ingested, not yet published. Atlas holds this source but no published relation carries it yet, so there is no query to run against the public API. Its rows are in Atlas; the modelling that would expose them has not been done. See meta_sources.served_as — an empty value is exactly this state.

Citation​

Recommended citation
Husbanken. (n.d.). Statistikkbank — Bostøtte. Retrieved from https://www.husbanken.no/tall-og-analyse/. Available in Atlas at https://atlas.sovereignsky.no/datasets/husbanken-bostotte.
BibTeX
@misc{atlas_husbanken_bostotte,
author = {Husbanken},
title = {Statistikkbank — Bostøtte},
year = {n.d.},
url = {https://www.husbanken.no/tall-og-analyse/},
note = {Available in Atlas at https://atlas.sovereignsky.no/datasets/husbanken-bostotte}
}
Permalink
https://atlas.sovereignsky.no/datasets/husbanken-bostotte

About this source​

Husbanken publishes bostøtte (housing allowance) application counts, decision counts, payout counts, rejection counts and the paid-out kroner amount, per kommune, per year, through its public "Statistikkbank" Qlik Sense app. Atlas reaches this over the Qlik Engine API (WebSocket JSON-RPC 2.0, officially documented by Qlik), not Power BI as an earlier investigation assumed — see atlas-data/ingest/src/sources/husbanken-bostotte/README.md for the full mechanism, including why a single-page hypercube fetch fails and the paginated fetch this source uses instead.