BIZTRAC BETA
Construction of residential and non-residential buildings

HURUM HAANDVERK AS

Org. no. 823545452 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 29,000
Equity NOK 130,000
Incorporated 2019
Employees 5
Share capital NOK 30,000

HURUM HAANDVERK AS is registered as a limited company in Asker, Akershus with organisation number 823545452. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygg, rehabilitering tilbygg og det som naturlig ligger inn under dette. Investering i aksjer og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 29,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 29,000
Equity
NOK 130,000
Est. value
NOK 151,000

Financial health · 2024

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

Who owns HURUM HAANDVERK AS?

HEIDI BENTE ØYE ISAGER
HURUM HAANDVERK AS
NOK 2.1m rev. · NOK 29,000 profit

HURUM HAANDVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HURUM HAANDVERK AS

Who owns HURUM HAANDVERK AS?

HEIDI BENTE ØYE ISAGER is the largest registered owner, with 100.0%.

What is the revenue of HURUM HAANDVERK AS?

HURUM HAANDVERK AS had revenue of NOK 2.1m in 2024.

Who is the general manager of HURUM HAANDVERK AS?

Carsten Isager is registered as general manager of HURUM HAANDVERK AS.

Where is HURUM HAANDVERK AS based?

HURUM HAANDVERK AS has its business address in Tofte.

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.