biztrac. BETA
COMPANY REGISTER PROFILE
985196761 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of charities which distribute means themselves

BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI

Org. no. 985196761 Foundation (STI) Østre Toten Incorporated 2002 Active
Ownership graph ↗
Operating profit NOK −678,000
Equity NOK 18.7m
Incorporated 2002
Share capital NOK 5.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−678k kr).

BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI is registered as a foundation in Østre Toten, Innlandet with organisation number 985196761. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2002. Registered share capital is NOK 5.1m.

Key figures · 2025

Operating profit
NOK −678,000
▼ −202 %
Equity
NOK 18.7m
▲ +6 %
Est. value
NOK 17.8m

Financial health · 2025

Liquidity
3.78
Very good
Current assets ÷ current liabilities
Profitability
6.2%
Satisfactory
Return on total assets
Solidity
98.7%
Very good
Equity as a share of total capital

Who owns BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI?

No shareholders are registered for BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI

Where is BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI based?

BIRGIT OG NILS A DAHL S LEGAT TIL FORDEL FOR EN PROTESTANTISK DIAKONISSEKOMMUNITET I NORGE STI has its business address in Skreia.

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

Report a problem

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