biztrac. BETA
COMPANY REGISTER PROFILE
931761544 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

M. LILLESTU HOLDING AS

Org. no. 931761544 Limited company (AS) Ringsaker Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 68,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

M. LILLESTU HOLDING AS is registered as a limited company in Ringsaker, Innlandet with organisation number 931761544. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap. Selskapets formål skal være forvaltning av eierinteresser, og det som måtte stå i den forbindelse.”.

Key figures · 2025

Operating profit
NOK −4,000
▼ −34 %
Equity
NOK 68,000
▲ +45 %
Est. value
NOK 175,000

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
17.2%
Weak
Equity as a share of total capital

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

Who owns M. LILLESTU HOLDING AS?

M. LILLESTU HOLDING AS
· NOK −4,000 profit

M. LILLESTU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M. LILLESTU HOLDING AS own?

M. LILLESTU HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about M. LILLESTU HOLDING AS

Who owns M. LILLESTU HOLDING AS?

Mikal Lillestu is the largest registered owner, with 100.0%.

Who is the general manager of M. LILLESTU HOLDING AS?

Mikal Lillestu is registered as general manager of M. LILLESTU HOLDING AS.

Where is M. LILLESTU HOLDING AS based?

M. LILLESTU HOLDING AS has its business address in Brøttum.

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.