BIZTRAC BETA
Rental and operating of own or leased real estate

HEISTAD BYGG OG EIENDOM AS

Org. no. 921331827 Limited company (AS) Porsgrunn Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 183,000
Operating profit NOK 86,000
Equity NOK 1.1m
Incorporated 2018
Share capital NOK 300,000

HEISTAD BYGG OG EIENDOM AS is registered as a limited company in Porsgrunn, Telemark with organisation number 921331827. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Utleie av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 183,000 in revenue and NOK 86,000 in operating profit.

Key figures · 2024

Revenue
NOK 183,000
Operating profit
NOK 86,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns HEISTAD BYGG OG EIENDOM AS?

AB-MARITIM AS
HEISTAD BYGG OG EIENDOM AS
NOK 183,000 rev. · NOK 86,000 profit

HEISTAD BYGG OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEISTAD BYGG OG EIENDOM AS

Who owns HEISTAD BYGG OG EIENDOM AS?

AB-MARITIM AS is the largest registered owner, with 100.0%.

What is the revenue of HEISTAD BYGG OG EIENDOM AS?

HEISTAD BYGG OG EIENDOM AS had revenue of NOK 183,000 in 2024.

Who is the general manager of HEISTAD BYGG OG EIENDOM AS?

Jarl Frode Kamfjord is registered as general manager of HEISTAD BYGG OG EIENDOM AS.

Where is HEISTAD BYGG OG EIENDOM AS based?

HEISTAD BYGG OG EIENDOM AS has its business address in Porsgrunn.

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.