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

STIFTELSEN BJØRGVIN KIRKELIGE FOND

Org. no. 971348674 Foundation (STI) Bergen Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.8m
Equity NOK 40.3m
Incorporated 1995
Share capital NOK 25.0m

STIFTELSEN BJØRGVIN KIRKELIGE FOND is registered as a foundation in Bergen, Vestland with organisation number 971348674. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 1995. Registered share capital is NOK 25.0m. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.8m in operating profit.

Former names: BJØRGVIN STIFTSSENTER

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.8m
▲ +2904 %
Equity
NOK 40.3m
▲ +9 %
Est. value
NOK 25.9m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns STIFTELSEN BJØRGVIN KIRKELIGE FOND?

No shareholders are registered for STIFTELSEN BJØRGVIN KIRKELIGE FOND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN BJØRGVIN KIRKELIGE FOND

What is the revenue of STIFTELSEN BJØRGVIN KIRKELIGE FOND?

STIFTELSEN BJØRGVIN KIRKELIGE FOND had revenue of NOK 1.9m in 2025.

Who is the general manager of STIFTELSEN BJØRGVIN KIRKELIGE FOND?

Christer Olsen is registered as general manager of STIFTELSEN BJØRGVIN KIRKELIGE FOND.

Where is STIFTELSEN BJØRGVIN KIRKELIGE FOND based?

STIFTELSEN BJØRGVIN KIRKELIGE FOND has its business address in Bergen.

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.