BIZTRAC BETA
Other specialised construction activities n.e.c.

SKJØNHAUG BETONG AS

Org. no. 923680403 Limited company (AS) Askøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 152,000
Equity NOK 243,000
Incorporated 2019
Employees 6
Share capital NOK 110,000

SKJØNHAUG BETONG AS is registered as a limited company in Askøy, Vestland with organisation number 923680403. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 110,000, divided into 1100 shares. The company's stated purpose is: “Muring og betongarbeid samt det som naturlig måtte falle inn under dette herunder kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 152,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 152,000
Equity
NOK 243,000
Est. value
NOK 611,000

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.0%
Good
Equity as a share of total capital

Who owns SKJØNHAUG BETONG AS?

KIM ANDRE SKJØNHAUG
SKJØNHAUG BETONG AS
NOK 5.0m rev. · NOK 152,000 profit

SKJØNHAUG BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKJØNHAUG BETONG AS

Who owns SKJØNHAUG BETONG AS?

KIM ANDRE SKJØNHAUG is the largest registered owner, with 100.0%.

What is the revenue of SKJØNHAUG BETONG AS?

SKJØNHAUG BETONG AS had revenue of NOK 5.0m in 2025.

Who is the general manager of SKJØNHAUG BETONG AS?

Kim Andre Skjønhaug is registered as general manager of SKJØNHAUG BETONG AS.

Where is SKJØNHAUG BETONG AS based?

SKJØNHAUG BETONG AS has its business address in Hetlevik.

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.