BIZTRAC BETA
Construction of residential and non-residential buildings

LANGFJORDEN BYGG AS

Org. no. 924479949 Limited company (AS) Molde Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK 565,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 60,000

LANGFJORDEN BYGG AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 924479949. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Oppføring av nybygg, tilbygg, restaurering av bygninger samt alt som naturlig faller sammen med dette, herunder deltagelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK 565,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK 565,000
Equity
NOK 1.1m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns LANGFJORDEN BYGG AS?

HÅVARD KOLSTAD
LANGFJORDEN BYGG AS
NOK 5.1m rev. · NOK 565,000 profit

LANGFJORDEN BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LANGFJORDEN BYGG AS

Who owns LANGFJORDEN BYGG AS?

HÅVARD KOLSTAD is the largest registered owner, with 50.0%.

What is the revenue of LANGFJORDEN BYGG AS?

LANGFJORDEN BYGG AS had revenue of NOK 5.1m in 2024.

Who is the general manager of LANGFJORDEN BYGG AS?

Joakim Lange is registered as general manager of LANGFJORDEN BYGG AS.

Where is LANGFJORDEN BYGG AS based?

LANGFJORDEN BYGG AS has its business address in Vistdal.

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.