biztrac. BETA
COMPANY REGISTER PROFILE
996335070 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KANALSLETTA HOLDING AS

Org. no. 996335070 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −121,000
Equity NOK 117.5m
Incorporated 2010
Share capital NOK 240,000

Signals

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

KANALSLETTA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 996335070. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 240,000, divided into 59900 shares. The company's stated purpose is: “Eie aksjer i Kanalsletta AS, som igjen eier eiendommen gnr. 35, bnr 438 i Sola kommune, og gjennom dette eierskap drifte og utvikle eiendommen, samt hva som hermed står i forbindelse.”.

Former names: UNION NYSTIFTET 21 AS

Key figures · 2025

Operating profit
NOK −121,000
▼ −1 %
Equity
NOK 117.5m
▼ −4 %
Est. value
NOK 107.2m

Financial health · 2025

Liquidity
34.05
Very good
Current assets ÷ current liabilities
Profitability
0.2%
Not satisfactory
Return on total assets
Solidity
68.1%
Very good
Equity as a share of total capital

Who owns KANALSLETTA HOLDING AS?

KANALSLETTA HOLDING AS
· NOK −121,000 profit

KANALSLETTA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KANALSLETTA HOLDING AS own?

KANALSLETTA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KANALSLETTA HOLDING AS

Who owns KANALSLETTA HOLDING AS?

H.I.G. PETRO AS is the largest registered owner, with 100.0%.

Where is KANALSLETTA HOLDING AS based?

KANALSLETTA HOLDING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.