biztrac. BETA
COMPANY REGISTER PROFILE
932170353 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computing infrastructure, data processing, hosting and related activities

MILLUM HOLDCO AS

Org. no. 932170353 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −124,000
Equity NOK 123.0m
Incorporated 2023
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−124k kr).

MILLUM HOLDCO AS is registered as a limited company in Bærum, Akershus with organisation number 932170353. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2023. Registered share capital is NOK 1.2m, divided into 1232696 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper og gjennomføre investeringer og virksomhet i forbindelse med dette.”.

Former names: ATHOMSTART INVEST 911 AS

Key figures · 2025

Operating profit
NOK −124,000
▲ +55 %
Equity
NOK 123.0m
▼ −0 %
Est. value
NOK 223.0m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns MILLUM HOLDCO AS?

MILLUM HOLDCO AS has 11 registered shareholders:

All shareholders and roles →

Which companies does MILLUM HOLDCO AS own?

MILLUM HOLDCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MILLUM HOLDCO AS

Who owns MILLUM HOLDCO AS?

MAIN FOUNDATION I COÖPERATLEF U.A is the largest registered owner, with 69.4%.

Who is the general manager of MILLUM HOLDCO AS?

Bjørn Anskau is registered as general manager of MILLUM HOLDCO AS.

Where is MILLUM HOLDCO AS based?

MILLUM HOLDCO AS has its business address in Fornebu.

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.