BIZTRAC BETA
Rental and operating of own or leased real estate

H HEITMANN & SON AS

Org. no. 918199764 Limited company (AS) Frogn Incorporated 1964 Active
Ownership graph ↗
Revenue 2024 NOK 17.1m
Operating profit NOK 4.6m
Equity NOK 18.8m
Incorporated 1964
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

H HEITMANN & SON AS is registered as a limited company in Frogn, Akershus with organisation number 918199764. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1964. Registered share capital is NOK 1.0m. The company's stated purpose is: “Spedisjon og befraktning, administrasjonsvirksom- het, finansiering, ervervelse og drift av fast eiendommer, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.1m in revenue and NOK 4.6m in operating profit.

Key figures · 2024

Revenue
NOK 17.1m
Operating profit
NOK 4.6m
Equity
NOK 18.8m
Est. value
NOK 22.2m

Financial health · 2024

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

Who owns H HEITMANN & SON AS?

ROUCAS AS
H HEITMANN & SON AS
NOK 17.1m rev. · NOK 4.6m profit

H HEITMANN & SON AS has 2 registered shareholders:

All shareholders and roles →

Group structure

H HEITMANN & SON AS er morselskap for 1 datterselskap:

Frequently asked questions about H HEITMANN & SON AS

Who owns H HEITMANN & SON AS?

ROUCAS AS is the largest registered owner, with 50.5%.

What is the revenue of H HEITMANN & SON AS?

H HEITMANN & SON AS had revenue of NOK 17.1m in 2024.

Where is H HEITMANN & SON AS based?

H HEITMANN & SON AS has its business address in Drøbak.

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.