BIZTRAC BETA
Rental and operating of own or leased real estate

VHF UTVIKLING AS

Org. no. 929361466 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK −14,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−14k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

VHF UTVIKLING AS is registered as a limited company in Bergen, Vestland with organisation number 929361466. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å investere i aksjer, obligasjoner og andre verdipapirer i selskaper, utvikle, kjøp, salg og utleie av fast eiendom ellers, samt investering i selskaper innenfor eiendom og eiendomsutvikling, tilsyns- og annen eierskapsvirksomhet med selskapets investeringer, utøve morselskapsfunksjoner på kontrollerende poster, samt alt annet som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK −14,000

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1236.9%
Weak
Equity as a share of total capital

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

Who owns VHF UTVIKLING AS?

FORLAND HOLDING AS
VHF UTVIKLING AS
· NOK −14,000 profit

VHF UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VHF UTVIKLING AS

Who owns VHF UTVIKLING AS?

FORLAND HOLDING AS is the largest registered owner, with 50.0%.

Where is VHF UTVIKLING AS based?

VHF UTVIKLING AS has its business address in Søreidgrend.

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.