BIZTRAC BETA
Uoppgitt

ALKE INVESTERINGER AS

Org. no. 935239052 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 77,000
Incorporated 2025
Share capital NOK 100,000

Signals

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

ALKE INVESTERINGER AS is registered as a limited company in Tromsø, Troms with organisation number 935239052. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Holdingselskap. Deltagelse i andre virksomheter ved selskapsinvesteringer og annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 77,000
Est. value
NOK 90,000

Financial health · 2025

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

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

Who owns ALKE INVESTERINGER AS?

C.B.M. AS
ALKE INVESTERINGER AS
NOK 0 rev. · NOK −15,000 profit

ALKE INVESTERINGER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ALKE INVESTERINGER AS own?

ALKE INVESTERINGER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALKE INVESTERINGER AS

Who owns ALKE INVESTERINGER AS?

C.B.M. AS is the largest registered owner, with 50.0%.

What is the revenue of ALKE INVESTERINGER AS?

ALKE INVESTERINGER AS had revenue of NOK 0 in 2025.

Where is ALKE INVESTERINGER AS based?

ALKE INVESTERINGER AS has its business address in Tromsø.

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.