BIZTRAC BETA
Development of building projects

KANALBYEN EIENDOM AS

Org. no. 911558688 Limited company (AS) Kristiansand Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 99.2m
Operating profit NOK −39.1m
Equity NOK 152.3m
Incorporated 2013
Share capital NOK 40.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−39,1 mill kr).

KANALBYEN EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 911558688. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 40.0m, divided into 30000 shares. The company's stated purpose is: “Eie, utvikle, drifte og selge fast eiendom samt eie aksjer i selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 99.2m in revenue and NOK −39.1m in operating profit.

Key figures · 2025

Revenue
NOK 99.2m
Operating profit
NOK −39.1m
Equity
NOK 152.3m
Est. value
NOK 221.6m

Financial health · 2025

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

Who owns KANALBYEN EIENDOM AS?

KANALBYEN PARTNER AS
KANALBYEN EIENDOM AS
NOK 99.2m rev. · NOK −39.1m profit

KANALBYEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KANALBYEN EIENDOM AS

Who owns KANALBYEN EIENDOM AS?

KANALBYEN PARTNER AS is the largest registered owner, with 100.0%.

What is the revenue of KANALBYEN EIENDOM AS?

KANALBYEN EIENDOM AS had revenue of NOK 99.2m in 2025.

Who is the general manager of KANALBYEN EIENDOM AS?

Sven Erik Knoph is registered as general manager of KANALBYEN EIENDOM AS.

Where is KANALBYEN EIENDOM AS based?

KANALBYEN EIENDOM AS has its business address in Kristiansand S.

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.