BIZTRAC BETA
Rental and operating of own or leased real estate

HUNSØYA UTVIKLING AS

Org. no. 929305086 Limited company (AS) Vennesla Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 510,000
Incorporated 2022
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HUNSØYA UTVIKLING AS is registered as a limited company in Vennesla, Agder with organisation number 929305086. 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 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andeler og det som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −28,000
Equity
NOK 510,000
Est. value
NOK 465,000

Financial health · 2025

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

Who owns HUNSØYA UTVIKLING AS?

GOD DRIV AS
HUNSØYA UTVIKLING AS
· NOK −28,000 profit

HUNSØYA UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HUNSØYA UTVIKLING AS own?

HUNSØYA UTVIKLING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HUNSØYA UTVIKLING AS

Who owns HUNSØYA UTVIKLING AS?

GOD DRIV AS is the largest registered owner, with 100.0%.

Who is the general manager of HUNSØYA UTVIKLING AS?

Thor Helle is registered as general manager of HUNSØYA UTVIKLING AS.

Where is HUNSØYA UTVIKLING AS based?

HUNSØYA UTVIKLING AS has its business address in Vennesla.

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.