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

VITOMAL INVEST AS

Org. no. 912299945 Limited company (AS) Oslo Incorporated 2013 Active
Revenue 2025 NOK 1,000,000
Operating profit NOK 780,000
Equity NOK 1.9m
Incorporated 2013
Share capital NOK 30,000

VITOMAL INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 912299945. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i og forvalte eiendommer, investerer i aksjer og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1,000,000 in revenue and NOK 780,000 in operating profit.

Key figures · 2025

Revenue
NOK 1,000,000
▲ +2 %
Operating profit
NOK 780,000
▲ +6 %
Equity
NOK 1.9m
▲ +31 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
16.2%
Very good
Return on total assets
Solidity
40.8%
Very good
Equity as a share of total capital

Who owns VITOMAL INVEST AS?

VITOMAL INVEST AS
NOK 1,000,000 rev. · NOK 780,000 profit

VITOMAL INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VITOMAL INVEST AS

Who owns VITOMAL INVEST AS?

RINDAL KLOSTER INVEST AS is the largest registered owner, with 50.3%.

What is the revenue of VITOMAL INVEST AS?

VITOMAL INVEST AS had revenue of NOK 1,000,000 in 2025.

Who is the general manager of VITOMAL INVEST AS?

Tom Rindal is registered as general manager of VITOMAL INVEST AS.

Where is VITOMAL INVEST AS based?

VITOMAL INVEST AS has its business address in Oslo.

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.