BIZTRAC BETA
Business and other management consultancy activities

DALEHAUG CONSULTING AS

Org. no. 912861422 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 813,000
Equity NOK 3.9m
Incorporated 2013
Share capital NOK 50,000

DALEHAUG CONSULTING AS is registered as a limited company in Bergen, Vestland with organisation number 912861422. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Salg av kunnskaper og produktutvikling til andre selskaper og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 813,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 813,000
Equity
NOK 3.9m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns DALEHAUG CONSULTING AS?

DALEHAUG HOLDING AS
DALEHAUG CONSULTING AS
NOK 1.8m rev. · NOK 813,000 profit

DALEHAUG CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DALEHAUG CONSULTING AS

Who owns DALEHAUG CONSULTING AS?

DALEHAUG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DALEHAUG CONSULTING AS?

DALEHAUG CONSULTING AS had revenue of NOK 1.8m in 2025.

Where is DALEHAUG CONSULTING AS based?

DALEHAUG CONSULTING AS has its business address in Bergen.

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

Report a problem

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