biztrac. BETA
COMPANY REGISTER PROFILE
995306360 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
All other professional, scientific and technical activities n.e.c.

NORSK KLIMASTIFTELSE

Org. no. 995306360 Foundation (STI) Bergen Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 496,000
Equity NOK 3.4m
Incorporated 2010
Employees 10
Share capital NOK 100,000

NORSK KLIMASTIFTELSE is registered as a foundation in Bergen, Vestland with organisation number 995306360. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2010 and has 10 registered employees. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 496,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
▼ −7 %
Operating profit
NOK 496,000
▲ +62 %
Equity
NOK 3.4m
▲ +17 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
5.4%
Weak
Return on total assets
Solidity
33.6%
Good
Equity as a share of total capital

Who owns NORSK KLIMASTIFTELSE?

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

Which companies does NORSK KLIMASTIFTELSE own?

NORSK KLIMASTIFTELSE holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORSK KLIMASTIFTELSE

What is the revenue of NORSK KLIMASTIFTELSE?

NORSK KLIMASTIFTELSE had revenue of NOK 13.0m in 2025.

Who is the general manager of NORSK KLIMASTIFTELSE?

Lars-Henrik Paarup Michelsen is registered as general manager of NORSK KLIMASTIFTELSE.

Where is NORSK KLIMASTIFTELSE based?

NORSK KLIMASTIFTELSE 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.