biztrac. BETA
COMPANY REGISTER PROFILE
934677242 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

VIK INVEST AS

Org. no. 934677242 Limited company (AS) Bærum Incorporated 1974 Active
Ownership graph ↗
Revenue 2025 NOK 60,000
Operating profit NOK 44,000
Equity NOK 4.2m
Incorporated 1974
Share capital NOK 306,000

VIK INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 934677242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1974. Registered share capital is NOK 306,000, divided into 1500 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendommer og deltagelse i andre selskaper, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 60,000 in revenue and NOK 44,000 in operating profit.

Former names: AS MALMØYA EIENDOMMER

Key figures · 2025

Revenue
NOK 60,000
▲ +0 %
Operating profit
NOK 44,000
▲ +0 %
Equity
NOK 4.2m
▲ +0 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
3.9%
Weak
Return on total assets
Solidity
14.2%
Satisfactory
Equity as a share of total capital

Who owns VIK INVEST AS?

VIK INVEST AS
NOK 60,000 rev. · NOK 44,000 profit

VIK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIK INVEST AS own?

VIK INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIK INVEST AS

Who owns VIK INVEST AS?

Ingar Andreas Imerslund is the largest registered owner, with 100.0%.

What is the revenue of VIK INVEST AS?

VIK INVEST AS had revenue of NOK 60,000 in 2025.

Where is VIK INVEST AS based?

VIK INVEST AS has its business address in Vøyenenga.

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.