BIZTRAC BETA
Graphic design and visual communication activities

MULTISCAN AS

Org. no. 914738598 Limited company (AS) Rollag Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 197,000
Operating profit NOK 72,000
Equity NOK 124,000
Incorporated 2014
Share capital NOK 50,000

MULTISCAN AS is registered as a limited company in Rollag, Buskerud with organisation number 914738598. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2014. Registered share capital is NOK 50,000, divided into 30 shares. The company's stated purpose is: “3D Skanning, digital laserskanning, eiendom, industri, taksering, salg av eiendom, dokumentasjon. Kjøp og salg av aksjer og eiendom. Alt som dertil hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 197,000 in revenue and NOK 72,000 in operating profit.

Key figures · 2025

Revenue
NOK 197,000
Operating profit
NOK 72,000
Equity
NOK 124,000
Est. value
NOK 291,000

Financial health · 2025

Liquidity
19.99
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.2%
Good
Equity as a share of total capital

Who owns MULTISCAN AS?

KÅRE KÅSIN
MULTISCAN AS
NOK 197,000 rev. · NOK 72,000 profit

MULTISCAN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MULTISCAN AS own?

MULTISCAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MULTISCAN AS

Who owns MULTISCAN AS?

KÅRE KÅSIN is the largest registered owner, with 80.0%.

What is the revenue of MULTISCAN AS?

MULTISCAN AS had revenue of NOK 197,000 in 2025.

Who is the general manager of MULTISCAN AS?

Kirsten Rosita Kåsin is registered as general manager of MULTISCAN AS.

Where is MULTISCAN AS based?

MULTISCAN AS has its business address in Veggli.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.