BIZTRAC BETA
Construction of residential and non-residential buildings

HARPER BYGG AS

Org. no. 996801691 Limited company (AS) Bærum Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 12.5m
Operating profit NOK 3.9m
Equity NOK 9.4m
Incorporated 2011
Share capital NOK 100,000

HARPER BYGG AS is registered as a limited company in Bærum, Akershus with organisation number 996801691. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Fremstilling/salg av håndverkertjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.5m in revenue and NOK 3.9m in operating profit.

Key figures · 2024

Revenue
NOK 12.5m
Operating profit
NOK 3.9m
Equity
NOK 9.4m
Est. value
NOK 17.0m

Financial health · 2024

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

Who owns HARPER BYGG AS?

FRITT FALL LTD NUF
HARPER BYGG AS
NOK 12.5m rev. · NOK 3.9m profit

HARPER BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HARPER BYGG AS

Who owns HARPER BYGG AS?

FRITT FALL LTD NUF is the largest registered owner, with 100.0%.

What is the revenue of HARPER BYGG AS?

HARPER BYGG AS had revenue of NOK 12.5m in 2024.

Who is the general manager of HARPER BYGG AS?

Karl Herbert Harper is registered as general manager of HARPER BYGG AS.

Where is HARPER BYGG AS based?

HARPER BYGG AS has its business address in Haslum.

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.