biztrac. BETA
COMPANY REGISTER PROFILE
824468192 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

VANIR AS

Org. no. 824468192 Limited company (AS) Sandefjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 144,000
Operating profit NOK −295,000
Equity NOK 202.8m
Incorporated 2020
Share capital NOK 60,000

Signals

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

VANIR AS is registered as a limited company in Sandefjord, Vestfold with organisation number 824468192. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Ledelsesrådgivning, investeringer i virksomheter. Annen virksomhet som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 144,000 in revenue and NOK −295,000 in operating profit.

Key figures · 2025

Revenue
NOK 144,000
▲ +242 %
Operating profit
NOK −295,000
▲ +81 %
Equity
NOK 202.8m
▼ −0 %
Est. value
NOK 99.0m

Financial health · 2025

Liquidity
15.28
Very good
Current assets ÷ current liabilities
Profitability
0.1%
Not satisfactory
Return on total assets
Solidity
86.6%
Very good
Equity as a share of total capital

Who owns VANIR AS?

VANIR AS
NOK 144,000 rev. · NOK −295,000 profit

VANIR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VANIR AS own?

VANIR AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about VANIR AS

Who owns VANIR AS?

TEKNOVEKST AS is the largest registered owner, with 100.0%.

What is the revenue of VANIR AS?

VANIR AS had revenue of NOK 144,000 in 2025.

Where is VANIR AS based?

VANIR AS has its business address in Sandefjord.

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.