BIZTRAC BETA
COMPANY REGISTER PROFILE
880871552 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

VEF UTVIKLING AS

Org. no. 880871552 Limited company (AS) Vennesla Incorporated 1999 Active
Ownership graph ↗
Operating profit NOK −130,000
Equity NOK 29.7m
Incorporated 1999
Share capital NOK 4.7m

Signals

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

VEF UTVIKLING AS is registered as a limited company in Vennesla, Agder with organisation number 880871552. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1999. Registered share capital is NOK 4.7m, divided into 1050 shares. The company's stated purpose is: “Å eie aksjer i selskaper innenfor entreprenørvirksomhet, drift og utvikling av eiendommer samt alt som hermed står i forbindelse herunder delta i selskaper med lignende virksomhet.”.

Former names: VENNESLA ENTREPRENØRFORRETNING EIENDOM AS

Key figures · 2025

Operating profit
NOK −130,000
▲ +37 %
Equity
NOK 29.7m
▲ +1 %
Est. value
NOK 29.7m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
7.8%
Satisfactory
Return on total assets
Solidity
92.8%
Very good
Equity as a share of total capital

Who owns VEF UTVIKLING AS?

VEF UTVIKLING AS has 8 registered shareholders:

All shareholders and roles →

Which companies does VEF UTVIKLING AS own?

VEF UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEF UTVIKLING AS

Who owns VEF UTVIKLING AS?

H. Q. EIENDOM AS is the largest registered owner, with 16.0%.

Who is the general manager of VEF UTVIKLING AS?

Håkon Honnemyr is registered as general manager of VEF UTVIKLING AS.

Where is VEF UTVIKLING AS based?

VEF 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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.