BIZTRAC BETA
Uoppgitt

ALEXANDER LONGUM OLSEN HOLDING AS

Org. no. 930572411 Limited company (AS) Skien Incorporated 2022 Active
Ownership graph ↗
Equity NOK 24,000
Incorporated 2022
Share capital NOK 30,000

ALEXANDER LONGUM OLSEN HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 930572411. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2024

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

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

Who owns ALEXANDER LONGUM OLSEN HOLDING AS?

ALEXANDER LONGUM OLSEN
ALEXANDER LONGUM OLSEN HOLDING AS

ALEXANDER LONGUM OLSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALEXANDER LONGUM OLSEN HOLDING AS own?

ALEXANDER LONGUM OLSEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ALEXANDER LONGUM OLSEN HOLDING AS

Who owns ALEXANDER LONGUM OLSEN HOLDING AS?

ALEXANDER LONGUM OLSEN is the largest registered owner, with 100.0%.

Who is the general manager of ALEXANDER LONGUM OLSEN HOLDING AS?

Alexander Longum Olsen is registered as general manager of ALEXANDER LONGUM OLSEN HOLDING AS.

Where is ALEXANDER LONGUM OLSEN HOLDING AS based?

ALEXANDER LONGUM OLSEN HOLDING AS has its business address in Skien.

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.