BIZTRAC BETA
Civil engineering activities

AUSTERDALEN BYGG AS

Org. no. 998015812 Limited company (AS) Kvinesdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 28.8m
Operating profit NOK 2.2m
Equity NOK 2.7m
Incorporated 2012
Employees 8
Share capital NOK 90,000

AUSTERDALEN BYGG AS is registered as a limited company in Kvinesdal, Agder with organisation number 998015812. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 90,000, divided into 300 shares. The company's stated purpose is: “Bygningsentreprenør med hva som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.8m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 28.8m
Operating profit
NOK 2.2m
Equity
NOK 2.7m
Est. value
NOK 12.4m

Financial health · 2025

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

Who owns AUSTERDALEN BYGG AS?

MORTEN SKJOLD
AUSTERDALEN BYGG AS
NOK 28.8m rev. · NOK 2.2m profit

AUSTERDALEN BYGG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does AUSTERDALEN BYGG AS own?

AUSTERDALEN BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AUSTERDALEN BYGG AS

Who owns AUSTERDALEN BYGG AS?

MORTEN SKJOLD is the largest registered owner, with 25.0%.

What is the revenue of AUSTERDALEN BYGG AS?

AUSTERDALEN BYGG AS had revenue of NOK 28.8m in 2025.

Who is the general manager of AUSTERDALEN BYGG AS?

Steinar Farestad is registered as general manager of AUSTERDALEN BYGG AS.

Where is AUSTERDALEN BYGG AS based?

AUSTERDALEN BYGG AS has its business address in Kvinesdal.

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.