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

MULTI VISION AS

Org. no. 918026509 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 900,000
Operating profit NOK 829,000
Equity NOK 109,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MULTI VISION AS is registered as a limited company in Bergen, Vestland with organisation number 918026509. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet og investering i andre selskaper”. The most recent filed accounts, for the 2025 financial year, show NOK 900,000 in revenue and NOK 829,000 in operating profit.

Key figures · 2025

Revenue
NOK 900,000
▼ −25 %
Operating profit
NOK 829,000
▼ −27 %
Equity
NOK 109,000
▲ +0 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
192.7%
Very good
Return on total assets
Solidity
15.1%
Satisfactory
Equity as a share of total capital

Who owns MULTI VISION AS?

MULTI VISION AS
NOK 900,000 rev. · NOK 829,000 profit

MULTI VISION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MULTI VISION AS

Who owns MULTI VISION AS?

J.BAKKE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MULTI VISION AS?

MULTI VISION AS had revenue of NOK 900,000 in 2025.

Where is MULTI VISION AS based?

MULTI VISION AS has its business address in Søreidgrend.

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.