BIZTRAC BETA
Other captive investment companies

ALMLIDALEN INVEST AS

Org. no. 989234196 Limited company (AS) Hustadvika Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −180,000
Equity NOK 5.8m
Incorporated 2005
Share capital NOK 150,000

Signals

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

ALMLIDALEN INVEST AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 989234196. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 2500 shares. The company's stated purpose is: “Rådgivning og investering i fast eiendom, aksjer og andeler, samt deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −180,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −180,000
Equity
NOK 5.8m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns ALMLIDALEN INVEST AS?

JANNE OLIVA HUSTAD
ALMLIDALEN INVEST AS
NOK 0 rev. · NOK −180,000 profit

ALMLIDALEN INVEST AS has 9 registered shareholders:

All shareholders and roles →

Which companies does ALMLIDALEN INVEST AS own?

ALMLIDALEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALMLIDALEN INVEST AS

Who owns ALMLIDALEN INVEST AS?

JANNE OLIVA HUSTAD is the largest registered owner, with 20.0%.

What is the revenue of ALMLIDALEN INVEST AS?

ALMLIDALEN INVEST AS had revenue of NOK 0 in 2024.

Where is ALMLIDALEN INVEST AS based?

ALMLIDALEN INVEST AS has its business address in Lyngstad.

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.