biztrac. BETA
COMPANY REGISTER PROFILE
932374870 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

BF.HOLDING AS

Org. no. 932374870 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 12.4m
Incorporated 2023
Share capital NOK 46,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).
  • Nylig endring 2026-09-17 Adresseendring registrert 2026-09-17.

BF.HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932374870. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 46,000, divided into 255 shares. The company's stated purpose is: “Å investere i og eie aksjer, verdipapirer, selskapsandeler, og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
▲ +56 %
Equity
NOK 12.4m
▲ +3 %
Est. value
NOK 9.0m

Financial health · 2025

Liquidity
159.21
Very good
Current assets ÷ current liabilities
Profitability
3.0%
Weak
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns BF.HOLDING AS?

BF.HOLDING AS
NOK 0 rev. · NOK −21,000 profit

BF.HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BF.HOLDING AS own?

BF.HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BF.HOLDING AS

Who owns BF.HOLDING AS?

Bjørnar Finnøy is the largest registered owner, with 100.0%.

What is the revenue of BF.HOLDING AS?

BF.HOLDING AS had revenue of NOK 0 in 2025.

Where is BF.HOLDING AS based?

BF.HOLDING AS has its business address in Harøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.