BIZTRAC BETA
Development of building projects

HEIANE VEST AS

Org. no. 992282053 Limited company (AS) Stord Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 46.0m
Operating profit NOK 11.0m
Equity NOK 12.9m
Incorporated 2008
Share capital NOK 5.6m

Signals

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

HEIANE VEST AS is registered as a limited company in Stord, Vestland with organisation number 992282053. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2008. Registered share capital is NOK 5.6m, divided into 3000 shares. The company's stated purpose is: “Forvalte fast eiendom, herunder drift, kjøp, salg og oppføring av fast eiendom, samt å delta i foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 46.0m in revenue and NOK 11.0m in operating profit.

Key figures · 2024

Revenue
NOK 46.0m
Operating profit
NOK 11.0m
Equity
NOK 12.9m
Est. value
NOK 35.5m

Financial health · 2025

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

Who owns HEIANE VEST AS?

BOLIGPARTNER FINANS AS
HEIANE VEST AS
NOK 46.0m rev. · NOK 11.0m profit

HEIANE VEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEIANE VEST AS own?

HEIANE VEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HEIANE VEST AS

Who owns HEIANE VEST AS?

BOLIGPARTNER FINANS AS is the largest registered owner, with 100.0%.

What is the revenue of HEIANE VEST AS?

HEIANE VEST AS had revenue of NOK 46.0m in 2024.

Where is HEIANE VEST AS based?

HEIANE VEST AS has its business address in Stord.

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.