BIZTRAC BETA
Rental and operating of own or leased real estate

KANALTOMTA AS

Org. no. 812790242 Limited company (AS) Rana Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 4.0m
Equity NOK −394,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−394k kr).

KANALTOMTA AS is registered as a limited company in Rana, Nordland with organisation number 812790242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eiendomsdrift og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 4.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 4.0m
Equity
NOK −394,000
Est. value
NOK 15.8m

Financial health · 2024

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

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

Who owns KANALTOMTA AS?

RANA NÆRINGSPARK AS
KANALTOMTA AS
NOK 5.3m rev. · NOK 4.0m profit

KANALTOMTA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KANALTOMTA AS

Who owns KANALTOMTA AS?

RANA NÆRINGSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of KANALTOMTA AS?

KANALTOMTA AS had revenue of NOK 5.3m in 2024.

Where is KANALTOMTA AS based?

KANALTOMTA AS has its business address in Mo I Rana.

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.