biztrac. BETA
COMPANY REGISTER PROFILE
989242938 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

MORTEN SØRLI HOLDING AS

Org. no. 989242938 Limited company (AS) Lørenskog Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 3.4m
Incorporated 2005
Share capital NOK 100,000

Signals

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

MORTEN SØRLI HOLDING AS is registered as a limited company in Lørenskog, Akershus with organisation number 989242938. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og andeler samt deltagelse i selskaper med beslektet formål.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK 3.4m
▲ +1 %
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns MORTEN SØRLI HOLDING AS?

MORTEN SØRLI HOLDING AS
· NOK −16,000 profit

MORTEN SØRLI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MORTEN SØRLI HOLDING AS own?

MORTEN SØRLI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MORTEN SØRLI HOLDING AS

Who owns MORTEN SØRLI HOLDING AS?

Morten Sørli is the largest registered owner, with 100.0%.

Who is the general manager of MORTEN SØRLI HOLDING AS?

Morten Sørli is registered as general manager of MORTEN SØRLI HOLDING AS.

Where is MORTEN SØRLI HOLDING AS based?

MORTEN SØRLI HOLDING AS has its business address in Lørenskog.

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.