BIZTRAC BETA
Activities of employment placement agencies

VING INVEST AS

Org. no. 980224570 Limited company (AS) Jevnaker Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 18,000
Operating profit NOK −84,000
Equity NOK 3.6m
Incorporated 1998
Share capital NOK 100,000

Signals

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

VING INVEST AS is registered as a limited company in Jevnaker, Akershus with organisation number 980224570. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i verdipapirer, aksjer og andre selskaper, eiendom og lignende. Samt formidling og utleie av bemanningstjenester til privat og offentlig sektor.”. The most recent filed accounts, for the 2024 financial year, show NOK 18,000 in revenue and NOK −84,000 in operating profit.

Key figures · 2024

Revenue
NOK 18,000
Operating profit
NOK −84,000
Equity
NOK 3.6m
Est. value
NOK 15.4m

Financial health · 2024

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

Who owns VING INVEST AS?

HÅKON ELFVING
VING INVEST AS
NOK 18,000 rev. · NOK −84,000 profit

VING INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VING INVEST AS own?

VING INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VING INVEST AS

Who owns VING INVEST AS?

HÅKON ELFVING is the largest registered owner, with 100.0%.

What is the revenue of VING INVEST AS?

VING INVEST AS had revenue of NOK 18,000 in 2024.

Where is VING INVEST AS based?

VING INVEST AS has its business address in Jevnaker.

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.