BIZTRAC BETA
Non-specialised wholesale trade

MILNIK INVEST AS

Org. no. 817409512 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK −11,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

MILNIK INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 817409512. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsselskap og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK −11,000

Financial health · 2024

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

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

Who owns MILNIK INVEST AS?

DENNIS ROLAND DEN ROOVER
MILNIK INVEST AS
NOK 0 rev. · NOK −8,000 profit

MILNIK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MILNIK INVEST AS own?

MILNIK INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MILNIK INVEST AS

Who owns MILNIK INVEST AS?

DENNIS ROLAND DEN ROOVER is the largest registered owner, with 100.0%.

What is the revenue of MILNIK INVEST AS?

MILNIK INVEST AS had revenue of NOK 0 in 2024.

Where is MILNIK INVEST AS based?

MILNIK INVEST AS has its business address in Bekkestua.

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.