biztrac. BETA
COMPANY REGISTER PROFILE
921698593 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

VDVF AS

Org. no. 921698593 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 4.1m
Equity NOK 43.8m
Incorporated 2018
Share capital NOK 80,000

VDVF AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921698593. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 80,000, divided into 40014 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, utlånsvirksomhet, fast eiendom og annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
▲ +26 %
Operating profit
NOK 4.1m
▲ +26 %
Equity
NOK 43.8m
▲ +61 %
Est. value
NOK 36.6m

Financial health · 2025

Liquidity
2.74
Very good
Current assets ÷ current liabilities
Profitability
75.8%
Very good
Return on total assets
Solidity
64.0%
Very good
Equity as a share of total capital

Who owns VDVF AS?

VDVF AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VDVF AS own?

VDVF AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VDVF AS

Who owns VDVF AS?

CTJO AS is the largest registered owner, with 43.7%.

What is the revenue of VDVF AS?

VDVF AS had revenue of NOK 4.4m in 2025.

Who is the general manager of VDVF AS?

Frode Johansen is registered as general manager of VDVF AS.

Where is VDVF AS based?

VDVF AS has its business address in Jakobsli.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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