BIZTRAC BETA
Development of building projects

NÅ UTVIKLING AS

Org. no. 929888790 Limited company (AS) Flesberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 29,000
Operating profit NOK −83,000
Equity NOK 16,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−83k kr).

NÅ UTVIKLING AS is registered as a limited company in Flesberg, Buskerud with organisation number 929888790. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom og alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet. Utbygging og drift av vannanlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 29,000 in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 29,000
Operating profit
NOK −83,000
Equity
NOK 16,000
Est. value
NOK 55,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NÅ UTVIKLING AS?

GUNN HEGE HUSLENDE
NÅ UTVIKLING AS
NOK 29,000 rev. · NOK −83,000 profit

NÅ UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NÅ UTVIKLING AS

Who owns NÅ UTVIKLING AS?

GUNN HEGE HUSLENDE is the largest registered owner, with 100.0%.

What is the revenue of NÅ UTVIKLING AS?

NÅ UTVIKLING AS had revenue of NOK 29,000 in 2025.

Where is NÅ UTVIKLING AS based?

NÅ UTVIKLING AS has its business address in Lampeland.

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.