BIZTRAC BETA
Rental and operating of own or leased real estate

IVAR M ALVSVÅG AS

Org. no. 989202847 Limited company (AS) Bømlo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −394,000
Equity NOK 9.9m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−394k kr).

IVAR M ALVSVÅG AS is registered as a limited company in Bømlo, Vestland with organisation number 989202847. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og deltakelse i andre virksomheter eie og drive fast eiendom, samt hav og kystfiske.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −394,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −394,000
Equity
NOK 9.9m
Est. value
NOK 9.5m

Financial health · 2024

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

Who owns IVAR M ALVSVÅG AS?

IVAR MARTIN ALVSVÅG
IVAR M ALVSVÅG AS
NOK 0 rev. · NOK −394,000 profit

IVAR M ALVSVÅG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IVAR M ALVSVÅG AS own?

IVAR M ALVSVÅG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about IVAR M ALVSVÅG AS

Who owns IVAR M ALVSVÅG AS?

IVAR MARTIN ALVSVÅG is the largest registered owner, with 100.0%.

What is the revenue of IVAR M ALVSVÅG AS?

IVAR M ALVSVÅG AS had revenue of NOK 0 in 2024.

Where is IVAR M ALVSVÅG AS based?

IVAR M ALVSVÅG AS has its business address in Bremnes.

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.