BIZTRAC BETA
Other captive investment companies

ALF MAGNAR ALVSVÅG AS

Org. no. 989202790 Limited company (AS) Bømlo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −62,000
Equity NOK 4.7m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−62k kr).

ALF MAGNAR ALVSVÅG AS is registered as a limited company in Bømlo, Vestland with organisation number 989202790. The business is classified under other captive investment companies (NACE 64.323). 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 samt eie og drive fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −62,000
Equity
NOK 4.7m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns ALF MAGNAR ALVSVÅG AS?

ALF MAGNAR ALVSVÅG
ALF MAGNAR ALVSVÅG AS
NOK 0 rev. · NOK −62,000 profit

ALF MAGNAR ALVSVÅG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALF MAGNAR ALVSVÅG AS own?

ALF MAGNAR ALVSVÅG AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ALF MAGNAR ALVSVÅG AS

Who owns ALF MAGNAR ALVSVÅG AS?

ALF MAGNAR ALVSVÅG is the largest registered owner, with 100.0%.

What is the revenue of ALF MAGNAR ALVSVÅG AS?

ALF MAGNAR ALVSVÅG AS had revenue of NOK 0 in 2025.

Where is ALF MAGNAR ALVSVÅG AS based?

ALF MAGNAR 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.