BIZTRAC BETA
Other real estate activities on a fee or contract basis

THORLEIF SUNDE INVESTERING AS

Org. no. 921845669 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −518,000
Equity NOK 91.6m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−518k kr).

THORLEIF SUNDE INVESTERING AS is registered as a limited company in Oslo, Oslo with organisation number 921845669. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andeler og alt som herved står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −518,000
Equity
NOK 91.6m
Est. value
NOK 94.4m

Financial health · 2024

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

Who owns THORLEIF SUNDE INVESTERING AS?

THORLEIF SUNDE AKSJESELSKAP
THORLEIF SUNDE INVESTERING AS
· NOK −518,000 profit

THORLEIF SUNDE INVESTERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THORLEIF SUNDE INVESTERING AS own?

THORLEIF SUNDE INVESTERING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about THORLEIF SUNDE INVESTERING AS

Who owns THORLEIF SUNDE INVESTERING AS?

THORLEIF SUNDE AKSJESELSKAP is the largest registered owner, with 100.0%.

Who is the general manager of THORLEIF SUNDE INVESTERING AS?

Thorleif Sunde is registered as general manager of THORLEIF SUNDE INVESTERING AS.

Where is THORLEIF SUNDE INVESTERING AS based?

THORLEIF SUNDE INVESTERING AS has its business address in Oslo.

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.