BIZTRAC BETA
Other captive investment companies

MAGNE ALVSVÅG AS

Org. no. 889202912 Limited company (AS) Bømlo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −407,000
Equity NOK 10.6m
Incorporated 2005
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−407k kr).
  • Nylig endring 2026-04-08 Aksjekapital registrert 2026-04-08.

MAGNE ALVSVÅG AS is registered as a limited company in Bømlo, Vestland with organisation number 889202912. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 30,000, 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 −407,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −407,000
Equity
NOK 10.6m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns MAGNE ALVSVÅG AS?

MAGNE ALVSVÅG
MAGNE ALVSVÅG AS
NOK 0 rev. · NOK −407,000 profit

MAGNE ALVSVÅG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does MAGNE ALVSVÅG AS own?

MAGNE ALVSVÅG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MAGNE ALVSVÅG AS

Who owns MAGNE ALVSVÅG AS?

MAGNE ALVSVÅG is the largest registered owner, with 66.4%.

What is the revenue of MAGNE ALVSVÅG AS?

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

Where is MAGNE ALVSVÅG AS based?

MAGNE 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.