BIZTRAC BETA
Construction of residential and non-residential buildings

LANGDALEN BYGG AS

Org. no. 821387272 Limited company (AS) Våler Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −108,000
Equity NOK 62,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−108k kr).

LANGDALEN BYGG AS is registered as a limited company in Våler, Innlandet with organisation number 821387272. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Nybygg, tilbygg, rehabilitering.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −108,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −108,000
Equity
NOK 62,000
Est. value
NOK 378,000

Financial health · 2024

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.8%
Weak
Equity as a share of total capital

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

Who owns LANGDALEN BYGG AS?

MARI HURUM
LANGDALEN BYGG AS
NOK 1.0m rev. · NOK −108,000 profit

LANGDALEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGDALEN BYGG AS

Who owns LANGDALEN BYGG AS?

MARI HURUM is the largest registered owner, with 100.0%.

What is the revenue of LANGDALEN BYGG AS?

LANGDALEN BYGG AS had revenue of NOK 1.0m in 2024.

Who is the general manager of LANGDALEN BYGG AS?

Mari Hurum is registered as general manager of LANGDALEN BYGG AS.

Where is LANGDALEN BYGG AS based?

LANGDALEN BYGG AS has its business address in Våler I Solør.

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.