BIZTRAC BETA
COMPANY REGISTER PROFILE
988035661 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

HAUGEN RÅDGIVNING AS

Org. no. 988035661 Limited company (AS) Stryn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 722,000
Operating profit NOK 444,000
Equity NOK 14.9m
Incorporated 2005
Share capital NOK 100,000

HAUGEN RÅDGIVNING AS is registered as a limited company in Stryn, Vestland with organisation number 988035661. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innen tjenesteytende næring.”. The most recent filed accounts, for the 2025 financial year, show NOK 722,000 in revenue and NOK 444,000 in operating profit.

Key figures · 2025

Revenue
NOK 722,000
▲ +301 %
Operating profit
NOK 444,000
▲ +225 %
Equity
NOK 14.9m
▼ −2 %
Est. value
NOK 9.3m

Financial health · 2025

Liquidity
56.31
Very good
Current assets ÷ current liabilities
Profitability
5.8%
Weak
Return on total assets
Solidity
98.9%
Very good
Equity as a share of total capital

Who owns HAUGEN RÅDGIVNING AS?

HAUGEN RÅDGIVNING AS
NOK 722,000 rev. · NOK 444,000 profit

HAUGEN RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAUGEN RÅDGIVNING AS own?

HAUGEN RÅDGIVNING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HAUGEN RÅDGIVNING AS

Who owns HAUGEN RÅDGIVNING AS?

BJØRN AAGE HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of HAUGEN RÅDGIVNING AS?

HAUGEN RÅDGIVNING AS had revenue of NOK 722,000 in 2025.

Where is HAUGEN RÅDGIVNING AS based?

HAUGEN RÅDGIVNING AS has its business address in Innvik.

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.