BIZTRAC BETA
Development of building projects

B&M HOLDING AS

Org. no. 915597203 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 43,000
Operating profit NOK −33,000
Equity NOK 1.2m
Incorporated 2015
Share capital NOK 2.5m

Signals

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

B&M HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 915597203. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 2.5m, divided into 2530 shares. The company's stated purpose is: “Eiendomsinvestering og utvikling og annet som naturlig faller sammen med dette. Selskapet skal også drive med tilleggsarbeid, transport oppdrag i forbindelse med arbeid for andre. Kjøp, salg og utleie av utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 43,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 43,000
Operating profit
NOK −33,000
Equity
NOK 1.2m
Est. value
NOK 852,000

Financial health · 2025

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

Who owns B&M HOLDING AS?

BJØRN FÆRØY
B&M HOLDING AS
NOK 43,000 rev. · NOK −33,000 profit

B&M HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about B&M HOLDING AS

Who owns B&M HOLDING AS?

BJØRN FÆRØY is the largest registered owner, with 50.0%.

What is the revenue of B&M HOLDING AS?

B&M HOLDING AS had revenue of NOK 43,000 in 2025.

Who is the general manager of B&M HOLDING AS?

Bjørn Færøy is registered as general manager of B&M HOLDING AS.

Where is B&M HOLDING AS based?

B&M HOLDING AS has its business address in Mathopen.

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.