BIZTRAC BETA
Business and other management consultancy activities

SOGN KOMPETANSE AS

Org. no. 826908262 Limited company (AS) Årdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 25,000
Equity NOK 80,000
Incorporated 2021
Share capital NOK 525,000

SOGN KOMPETANSE AS is registered as a limited company in Årdal, Vestland with organisation number 826908262. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 525,000, divided into 525 shares. The company's stated purpose is: “Utvikling, sal og koordinering av kurs, opplæring, konferansar og andre tenester som naturleg fell saman med dette, samt å delta i andre selskap med liknande verksemd. Selskapet kan og delta som aksjonær, eller på anna måte ved investering i andre verksemder.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 25,000
Equity
NOK 80,000
Est. value
NOK 166,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SOGN KOMPETANSE AS?

ÅRDAL UTVIKLING STI
SOGN KOMPETANSE AS
NOK 3.5m rev. · NOK 25,000 profit

SOGN KOMPETANSE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOGN KOMPETANSE AS

Who owns SOGN KOMPETANSE AS?

ÅRDAL UTVIKLING STI is the largest registered owner, with 38.1%.

What is the revenue of SOGN KOMPETANSE AS?

SOGN KOMPETANSE AS had revenue of NOK 3.5m in 2025.

Where is SOGN KOMPETANSE AS based?

SOGN KOMPETANSE AS has its business address in Øvre Årdal.

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.