BIZTRAC BETA
Business and other management consultancy activities

VMK INVEST AS

Org. no. 912302652 Limited company (AS) Drammen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK 703,000
Equity NOK 15.5m
Incorporated 2013
Share capital NOK 30,000

VMK INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 912302652. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskap og økonomisk rådgivning og konsulentbistand.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK 703,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK 703,000
Equity
NOK 15.5m
Est. value
NOK 11.3m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
88.8%
Very good
Equity as a share of total capital

Who owns VMK INVEST AS?

ELISABETH LAMM-KITTELSEN BRATTERUD
VMK INVEST AS
NOK 2.6m rev. · NOK 703,000 profit

VMK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VMK INVEST AS own?

VMK INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VMK INVEST AS

Who owns VMK INVEST AS?

ELISABETH LAMM-KITTELSEN BRATTERUD is the largest registered owner, with 100.0%.

What is the revenue of VMK INVEST AS?

VMK INVEST AS had revenue of NOK 2.6m in 2024.

Who is the general manager of VMK INVEST AS?

Tomas Bratterud is registered as general manager of VMK INVEST AS.

Where is VMK INVEST AS based?

VMK INVEST AS has its business address in Drammen.

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.