BIZTRAC BETA
Development of building projects

HERSLETH UTVIKLING AS

Org. no. 919461675 Limited company (AS) Våler Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −128,000
Equity NOK 25.6m
Incorporated 2017
Share capital NOK 120,000

Signals

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

HERSLETH UTVIKLING AS is registered as a limited company in Våler, Østfold with organisation number 919461675. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 120,000, divided into 1202 shares. The company's stated purpose is: “Investeringer i andre selskap og eiendom samt utleie og handel av varer og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −128,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −128,000
Equity
NOK 25.6m
Est. value
NOK 17.6m

Financial health · 2024

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

Who owns HERSLETH UTVIKLING AS?

CH HERSLETH HOLDING AS
HERSLETH UTVIKLING AS
NOK 0 rev. · NOK −128,000 profit

HERSLETH UTVIKLING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HERSLETH UTVIKLING AS own?

HERSLETH UTVIKLING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HERSLETH UTVIKLING AS

Who owns HERSLETH UTVIKLING AS?

CH HERSLETH HOLDING AS is the largest registered owner, with 32.2%.

What is the revenue of HERSLETH UTVIKLING AS?

HERSLETH UTVIKLING AS had revenue of NOK 0 in 2024.

Where is HERSLETH UTVIKLING AS based?

HERSLETH UTVIKLING AS has its business address in Sperrebotn.

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.