BIZTRAC BETA
Rental and operating of own or leased real estate

KANALVEIEN 50 AS

Org. no. 885842232 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 54,000
Operating profit NOK −22,000
Equity NOK 164.9m
Incorporated 2003
Share capital NOK 200,000

Signals

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

KANALVEIEN 50 AS is registered as a limited company in Bergen, Vestland with organisation number 885842232. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drift av fast eiendom, herunder kjøp og salg av fast eiendom samt deltakelse i annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 54,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 54,000
Operating profit
NOK −22,000
Equity
NOK 164.9m
Est. value
NOK 120.7m

Financial health · 2024

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

Who owns KANALVEIEN 50 AS?

ELLJODD HOLDING AS
KANALVEIEN 50 AS
NOK 54,000 rev. · NOK −22,000 profit

KANALVEIEN 50 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KANALVEIEN 50 AS own?

KANALVEIEN 50 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KANALVEIEN 50 AS

Who owns KANALVEIEN 50 AS?

ELLJODD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KANALVEIEN 50 AS?

KANALVEIEN 50 AS had revenue of NOK 54,000 in 2024.

Where is KANALVEIEN 50 AS based?

KANALVEIEN 50 AS has its business address in Bergen.

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.