BIZTRAC BETA
Uoppgitt

MO-LO HOLDING AS

Org. no. 935265045 Limited company (AS) Gjerdrum Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

MO-LO HOLDING AS is registered as a limited company in Gjerdrum, Akershus with organisation number 935265045. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer, kjøp/salg av eiendom, utleie av eiendom, kjøp/salg av aksjer, deltakelse i andre selskaper og alt som naturlig faller her under.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns MO-LO HOLDING AS?

MORTEN LORENTZEN
MO-LO HOLDING AS
NOK 0 rev. · NOK 0 profit

MO-LO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MO-LO HOLDING AS own?

MO-LO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MO-LO HOLDING AS

Who owns MO-LO HOLDING AS?

MORTEN LORENTZEN is the largest registered owner, with 100.0%.

What is the revenue of MO-LO HOLDING AS?

MO-LO HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of MO-LO HOLDING AS?

Morten Lorentzen is registered as general manager of MO-LO HOLDING AS.

Where is MO-LO HOLDING AS based?

MO-LO HOLDING AS has its business address in Gjerdrum.

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.