BIZTRAC BETA
Rental and operating of own or leased real estate

HENSENGAN EIENDOM AS

Org. no. 924937017 Limited company (AS) Rauma Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 352,000
Operating profit NOK 65,000
Equity NOK 610,000
Incorporated 2020
Share capital NOK 770,000

HENSENGAN EIENDOM AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 924937017. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 770,000, divided into 770 shares. The company's stated purpose is: “Investere i og drive utleie av fast eiendom samt alt som står i forbindelse med dette, herunder å eie aksjer i andre selskaper i tilsvarende bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 352,000 in revenue and NOK 65,000 in operating profit.

Key figures · 2025

Revenue
NOK 352,000
Operating profit
NOK 65,000
Equity
NOK 610,000
Est. value
NOK 524,000

Financial health · 2025

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.5%
Good
Equity as a share of total capital

Who owns HENSENGAN EIENDOM AS?

KJETILL SANDNES
HENSENGAN EIENDOM AS
NOK 352,000 rev. · NOK 65,000 profit

HENSENGAN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENSENGAN EIENDOM AS

Who owns HENSENGAN EIENDOM AS?

KJETILL SANDNES is the largest registered owner, with 100.0%.

What is the revenue of HENSENGAN EIENDOM AS?

HENSENGAN EIENDOM AS had revenue of NOK 352,000 in 2025.

Who is the general manager of HENSENGAN EIENDOM AS?

Kjetill Sandnes is registered as general manager of HENSENGAN EIENDOM AS.

Where is HENSENGAN EIENDOM AS based?

HENSENGAN EIENDOM AS has its business address in Isfjorden.

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.