biztrac. BETA
COMPANY REGISTER PROFILE
960496760 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Technical testing and analysis

STIFTELSEN KONTROLLRÅDET

Org. no. 960496760 Foundation (STI) Oslo Incorporated 1967 Active
Ownership graph ↗
Revenue 2025 NOK 33.7m
Operating profit NOK 1.8m
Equity NOK 13.3m
Incorporated 1967
Employees 16
Share capital NOK 500,000

STIFTELSEN KONTROLLRÅDET is registered as a foundation in Oslo, Oslo with organisation number 960496760. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 1967 and has 16 registered employees. Registered share capital is NOK 500,000. The company's stated purpose is: “Ledende teknisk kontrollorgan innen sine virksomhetsområder.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.7m in revenue and NOK 1.8m in operating profit.

Former names: KONTROLLRÅDET FOR BETONG- PRODUKTER, STIFTELSEN KONTROLLRÅDET FOR BETONGPRODUKTER

Key figures · 2025

Revenue
NOK 33.7m
▼ −0 %
Operating profit
NOK 1.8m
▼ −16 %
Equity
NOK 13.3m
▲ +22 %
Est. value
NOK 17.4m

Financial health · 2025

Liquidity
3.51
Very good
Current assets ÷ current liabilities
Profitability
13.9%
Good
Return on total assets
Solidity
73.6%
Very good
Equity as a share of total capital

Who owns STIFTELSEN KONTROLLRÅDET?

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

Frequently asked questions about STIFTELSEN KONTROLLRÅDET

What is the revenue of STIFTELSEN KONTROLLRÅDET?

STIFTELSEN KONTROLLRÅDET had revenue of NOK 33.7m in 2025.

Who is the general manager of STIFTELSEN KONTROLLRÅDET?

Jørn Nikolai Haugen is registered as general manager of STIFTELSEN KONTROLLRÅDET.

Where is STIFTELSEN KONTROLLRÅDET based?

STIFTELSEN KONTROLLRÅDET has its business address in Oslo.

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.