BIZTRAC BETA
Rental and operating of own or leased real estate

HEKI HOLDING AS

Org. no. 988963305 Limited company (AS) Moss Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 21.1m
Incorporated 2005
Share capital NOK 100,000

Signals

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

HEKI HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 988963305. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Drive investeringsvirksomhet med aksjer og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 21.1m
Est. value
NOK 18.3m

Financial health · 2024

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

Who owns HEKI HOLDING AS?

KIM OTTER HANSEN
HEKI HOLDING AS
NOK 0 rev. · NOK −9,000 profit

HEKI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HEKI HOLDING AS own?

HEKI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HEKI HOLDING AS

Who owns HEKI HOLDING AS?

KIM OTTER HANSEN is the largest registered owner, with 50.0%.

What is the revenue of HEKI HOLDING AS?

HEKI HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of HEKI HOLDING AS?

Kim Otter Hansen is registered as general manager of HEKI HOLDING AS.

Where is HEKI HOLDING AS based?

HEKI HOLDING AS has its business address in Moss.

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.