BIZTRAC BETA
Construction of residential and non-residential buildings

MØLL BYGG AS

Org. no. 814348962 Limited company (AS) Lindesnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 6.4m
Operating profit NOK 88,000
Equity NOK 135,000
Incorporated 2014
Employees 5
Share capital NOK 40,000

MØLL BYGG AS is registered as a limited company in Lindesnes, Agder with organisation number 814348962. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Salg av snekkertjenester, samt handel og alt som naturlig faller inn under dette, herunder eie av andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.4m in revenue and NOK 88,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.4m
Operating profit
NOK 88,000
Equity
NOK 135,000
Est. value
NOK 359,000

Financial health · 2024

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

Who owns MØLL BYGG AS?

VEGAR MØLL
MØLL BYGG AS
NOK 6.4m rev. · NOK 88,000 profit

MØLL BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MØLL BYGG AS own?

MØLL BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MØLL BYGG AS

Who owns MØLL BYGG AS?

VEGAR MØLL is the largest registered owner, with 100.0%.

What is the revenue of MØLL BYGG AS?

MØLL BYGG AS had revenue of NOK 6.4m in 2024.

Who is the general manager of MØLL BYGG AS?

Vegar Møll is registered as general manager of MØLL BYGG AS.

Where is MØLL BYGG AS based?

MØLL BYGG AS has its business address in Holum.

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.