BIZTRAC BETA
Development of building projects

NÆRINGSBYGG HEIANE AS

Org. no. 992746165 Limited company (AS) Haugesund Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 1.8m
Equity NOK 1.7m
Incorporated 2008
Share capital NOK 100,000

Signals

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

NÆRINGSBYGG HEIANE AS is registered as a limited company in Haugesund, Rogaland with organisation number 992746165. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 1.8m
Equity
NOK 1.7m
Est. value
NOK 4.0m

Financial health · 2024

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.9%
Satisfactory
Equity as a share of total capital

Who owns NÆRINGSBYGG HEIANE AS?

HAUGLI EIENDOM AS
NÆRINGSBYGG HEIANE AS
NOK 2.5m rev. · NOK 1.8m profit

NÆRINGSBYGG HEIANE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NÆRINGSBYGG HEIANE AS

Who owns NÆRINGSBYGG HEIANE AS?

HAUGLI EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NÆRINGSBYGG HEIANE AS?

NÆRINGSBYGG HEIANE AS had revenue of NOK 2.5m in 2024.

Who is the general manager of NÆRINGSBYGG HEIANE AS?

Tor-Einar Sandvik is registered as general manager of NÆRINGSBYGG HEIANE AS.

Where is NÆRINGSBYGG HEIANE AS based?

NÆRINGSBYGG HEIANE AS has its business address in Haugesund.

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.