BIZTRAC BETA
Uoppgitt

KALAND INVEST AS

Org. no. 824061432 Limited company (AS) Sola Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK −176,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−176k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

KALAND INVEST AS is registered as a limited company in Sola, Rogaland with organisation number 824061432. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. 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 · 2025

Operating profit
NOK −10,000
Equity
NOK −176,000

Financial health · 2025

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

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

Who owns KALAND INVEST AS?

BJØRN ANDRE KALAND
KALAND INVEST AS
· NOK −10,000 profit

KALAND INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KALAND INVEST AS own?

KALAND INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KALAND INVEST AS

Who owns KALAND INVEST AS?

BJØRN ANDRE KALAND is the largest registered owner, with 100.0%.

Who is the general manager of KALAND INVEST AS?

Bjørn Andre Kaland is registered as general manager of KALAND INVEST AS.

Where is KALAND INVEST AS based?

KALAND INVEST AS has its business address in Røyneberg.

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.