BIZTRAC BETA
Site preparation

JØRUND HAUGLAND ENTREPRENØR AS

Org. no. 892798702 Limited company (AS) Alver Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 334,000
Equity NOK 1.3m
Incorporated 2008
Share capital NOK 100,000

JØRUND HAUGLAND ENTREPRENØR AS is registered as a limited company in Alver, Vestland with organisation number 892798702. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Selskapets virksomhet er å drive entrepenørvirksomhet og annen beslektet virksomhet samt oppføring av bygg.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 334,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 334,000
Equity
NOK 1.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns JØRUND HAUGLAND ENTREPRENØR AS?

JØRUND HAUGLAND
JØRUND HAUGLAND ENTREPRENØR AS
NOK 3.1m rev. · NOK 334,000 profit

JØRUND HAUGLAND ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JØRUND HAUGLAND ENTREPRENØR AS

Who owns JØRUND HAUGLAND ENTREPRENØR AS?

JØRUND HAUGLAND is the largest registered owner, with 100.0%.

What is the revenue of JØRUND HAUGLAND ENTREPRENØR AS?

JØRUND HAUGLAND ENTREPRENØR AS had revenue of NOK 3.1m in 2025.

Who is the general manager of JØRUND HAUGLAND ENTREPRENØR AS?

Jørund Haugland is registered as general manager of JØRUND HAUGLAND ENTREPRENØR AS.

Where is JØRUND HAUGLAND ENTREPRENØR AS based?

JØRUND HAUGLAND ENTREPRENØR AS has its business address in Bøvågen.

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.