BIZTRAC BETA
Uoppgitt

BABF HOLDING AS

Org. no. 830158332 Limited company (AS) Moss Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 2,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

BABF HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 830158332. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringer i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 2,000
Est. value
NOK 3,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BABF HOLDING AS?

BJØRG ANITA BJØRKÅ FLATIN
BABF HOLDING AS
NOK 0 rev. · NOK −10,000 profit

BABF HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BABF HOLDING AS own?

BABF HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BABF HOLDING AS

Who owns BABF HOLDING AS?

BJØRG ANITA BJØRKÅ FLATIN is the largest registered owner, with 100.0%.

What is the revenue of BABF HOLDING AS?

BABF HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of BABF HOLDING AS?

Bjørg Anita Bjørkå Flatin is registered as general manager of BABF HOLDING AS.

Where is BABF HOLDING AS based?

BABF HOLDING AS has its business address in Larkollen.

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.