biztrac. BETA
COMPANY REGISTER PROFILE
927312557 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Painting and glazing

VIMALIO AS

Org. no. 927312557 Limited company (AS) Bærum Incorporated 2021 Active
Revenue 2025 NOK 6.9m
Operating profit NOK −169,000
Equity NOK −305,000
Incorporated 2021
Employees 6
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−305k kr).

VIMALIO AS is registered as a limited company in Bærum, Akershus with organisation number 927312557. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Håndverkstjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK −169,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
▲ +17 %
Operating profit
NOK −169,000
▼ −6496 %
Equity
NOK −305,000
▼ −80 %

Financial health · 2025

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-21.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VIMALIO AS?

VIMALIO AS
NOK 6.9m rev. · NOK −169,000 profit

VIMALIO AS has 2 registered shareholders:

All shareholders and roles →

Group structure

VIMALIO AS er morselskap for 8 datterselskaper:

Frequently asked questions about VIMALIO AS

Who owns VIMALIO AS?

VIGRUPPEN AS is the largest registered owner, with 75.0%.

What is the revenue of VIMALIO AS?

VIMALIO AS had revenue of NOK 6.9m in 2025.

Who is the general manager of VIMALIO AS?

Vilmantas Urbonavicius is registered as general manager of VIMALIO AS.

Where is VIMALIO AS based?

VIMALIO AS has its business address in Rud.

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.