BIZTRAC BETA
Site preparation

HØLAND ENTREPRENØR AS

Org. no. 914404231 Limited company (AS) Aurskog-Høland Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 13.8m
Operating profit NOK −140,000
Equity NOK 4.8m
Incorporated 2014
Employees 9
Share capital NOK 100,000

Signals

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

HØLAND ENTREPRENØR AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 914404231. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet innen grunnarbeider”. The most recent filed accounts, for the 2024 financial year, show NOK 13.8m in revenue and NOK −140,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.8m
Operating profit
NOK −140,000
Equity
NOK 4.8m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns HØLAND ENTREPRENØR AS?

MORTEN NYSTUEN KRAGTORP
HØLAND ENTREPRENØR AS
NOK 13.8m rev. · NOK −140,000 profit

HØLAND ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØLAND ENTREPRENØR AS

Who owns HØLAND ENTREPRENØR AS?

MORTEN NYSTUEN KRAGTORP is the largest registered owner, with 100.0%.

What is the revenue of HØLAND ENTREPRENØR AS?

HØLAND ENTREPRENØR AS had revenue of NOK 13.8m in 2024.

Who is the general manager of HØLAND ENTREPRENØR AS?

Morten Nystuen Kragtorp is registered as general manager of HØLAND ENTREPRENØR AS.

Where is HØLAND ENTREPRENØR AS based?

HØLAND ENTREPRENØR AS has its business address in Hemnes.

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.