BIZTRAC BETA
COMPANY REGISTER PROFILE
996795292 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Family counselling services

STIFTELSEN KIRKENS FAMILIEVERN

Org. no. 996795292 Foundation (STI) Oslo Incorporated 2010 Active
Ownership graph ↗
Equity NOK 24.3m
Incorporated 2010
Employees 163
Share capital NOK 2.0m

STIFTELSEN KIRKENS FAMILIEVERN is registered as a foundation in Oslo, Oslo with organisation number 996795292. The business is classified under family counselling services (NACE 88.992). The company was incorporated in 2010 and has 163 registered employees. Registered share capital is NOK 2.0m.

Key figures · 2025

Equity
NOK 24.3m
Est. value
NOK 37.7m

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.5%
Good
Equity as a share of total capital

Who owns STIFTELSEN KIRKENS FAMILIEVERN?

No shareholders are registered for STIFTELSEN KIRKENS FAMILIEVERN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN KIRKENS FAMILIEVERN

Who is the general manager of STIFTELSEN KIRKENS FAMILIEVERN?

Hilde Johanne Barstad is registered as general manager of STIFTELSEN KIRKENS FAMILIEVERN.

Where is STIFTELSEN KIRKENS FAMILIEVERN based?

STIFTELSEN KIRKENS FAMILIEVERN has its business address in Oslo.

Property

Business address c/o Familievernkontoret Christiania Dronningens gate 8A, 0152 Oslo
Cadastral unit 301-207/34/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

7 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.