BIZTRAC BETA
Manufacture of communication equipment

A & MB HOLDING AS

Org. no. 989024086 Limited company (AS) Larvik Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 137,000
Operating profit NOK 15,000
Equity NOK 49.2m
Incorporated 2005
Share capital NOK 100,000

A & MB HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 989024086. The business is classified under manufacture of communication equipment (NACE 26.300). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andeler i andre virksomheter, kjøp og salg og utleie av fast eiendom, samt konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 137,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 137,000
Operating profit
NOK 15,000
Equity
NOK 49.2m
Est. value
NOK 26.1m

Financial health · 2024

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

Who owns A & MB HOLDING AS?

MERETE STAVIK BERDAL
A & MB HOLDING AS
NOK 137,000 rev. · NOK 15,000 profit

A & MB HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does A & MB HOLDING AS own?

A & MB HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

A & MB HOLDING AS er morselskap for 6 datterselskaper:

Frequently asked questions about A & MB HOLDING AS

Who owns A & MB HOLDING AS?

MERETE STAVIK BERDAL is the largest registered owner, with 100.0%.

What is the revenue of A & MB HOLDING AS?

A & MB HOLDING AS had revenue of NOK 137,000 in 2024.

Where is A & MB HOLDING AS based?

A & MB HOLDING AS has its business address in Larvik.

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.