BIZTRAC BETA
Computer consultancy and computer facilities management activities

ASCAN AS

Org. no. 922818363 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 25.6m
Operating profit NOK 8.8m
Equity NOK 12.0m
Incorporated 2019
Employees 11
Share capital NOK 100,000

ASCAN AS is registered as a limited company in Asker, Akershus with organisation number 922818363. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Fremstilling/salg av konsulenttjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.6m in revenue and NOK 8.8m in operating profit.

Key figures · 2025

Revenue
NOK 25.6m
Operating profit
NOK 8.8m
Equity
NOK 12.0m
Est. value
NOK 43.0m

Financial health · 2025

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

Who owns ASCAN AS?

ASKER HEALTHCARE AB
ASCAN AS
NOK 25.6m rev. · NOK 8.8m profit

ASCAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASCAN AS

Who owns ASCAN AS?

ASKER HEALTHCARE AB is the largest registered owner, with 100.0%.

What is the revenue of ASCAN AS?

ASCAN AS had revenue of NOK 25.6m in 2025.

Who is the general manager of ASCAN AS?

Bjørn Gregersen is registered as general manager of ASCAN AS.

Where is ASCAN AS based?

ASCAN AS has its business address in Vettre.

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.