BIZTRAC BETA
Construction of residential and non-residential buildings

JON HAUGLAND BYGG AS

Org. no. 925795097 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 743,000
Operating profit NOK 257,000
Equity NOK 266,000
Incorporated 2020
Share capital NOK 30,000

JON HAUGLAND BYGG AS is registered as a limited company in Asker, Akershus with organisation number 925795097. 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 30,000, divided into 10 shares. The company's stated purpose is: “Oppføring av bygg og tømrerarbeider generelt. Kjøp, salg og utleie av fast eiendom og det som herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 743,000 in revenue and NOK 257,000 in operating profit.

Key figures · 2025

Revenue
NOK 743,000
Operating profit
NOK 257,000
Equity
NOK 266,000
Est. value
NOK 798,000

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.5%
Good
Equity as a share of total capital

Who owns JON HAUGLAND BYGG AS?

COBRA HOLDING AS
JON HAUGLAND BYGG AS
NOK 743,000 rev. · NOK 257,000 profit

JON HAUGLAND BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JON HAUGLAND BYGG AS

Who owns JON HAUGLAND BYGG AS?

COBRA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JON HAUGLAND BYGG AS?

JON HAUGLAND BYGG AS had revenue of NOK 743,000 in 2025.

Who is the general manager of JON HAUGLAND BYGG AS?

Jon Terje Haugland is registered as general manager of JON HAUGLAND BYGG AS.

Where is JON HAUGLAND BYGG AS based?

JON HAUGLAND BYGG AS has its business address in Heggedal.

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.