BIZTRAC BETA
Business and other management consultancy activities

KJETIL VESTRUM CONSULTING AS

Org. no. 996569713 Limited company (AS) Larvik Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −124
Equity NOK 545,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−124 kr).

KJETIL VESTRUM CONSULTING AS is registered as a limited company in Larvik, Vestfold with organisation number 996569713. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bedriftsrådgivning og/eller annen administrative rådgivning og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −124
Equity
NOK 545,000
Est. value
NOK 555,000

Financial health · 2024

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

Who owns KJETIL VESTRUM CONSULTING AS?

KJETIL VESTRUM
KJETIL VESTRUM CONSULTING AS
· NOK −124 profit

KJETIL VESTRUM CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJETIL VESTRUM CONSULTING AS

Who owns KJETIL VESTRUM CONSULTING AS?

KJETIL VESTRUM is the largest registered owner, with 100.0%.

Who is the general manager of KJETIL VESTRUM CONSULTING AS?

Kjetil Vestrum is registered as general manager of KJETIL VESTRUM CONSULTING AS.

Where is KJETIL VESTRUM CONSULTING AS based?

KJETIL VESTRUM CONSULTING AS has its business address in Larvik.

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.