BIZTRAC BETA
Pre-primary education

BAGLERBYEN FUS BARNEHAGE AS

Org. no. 927310341 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 17.6m
Operating profit NOK 951,000
Equity NOK 1.6m
Incorporated 2019
Employees 26
Share capital NOK 433,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BAGLERBYEN FUS BARNEHAGE AS is registered as a limited company in Oslo, Oslo with organisation number 927310341. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2019 and has 26 registered employees. Registered share capital is NOK 433,000, divided into 100 shares. The company's stated purpose is: “Å drive barnehage.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.6m in revenue and NOK 951,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.6m
Operating profit
NOK 951,000
Equity
NOK 1.6m
Est. value
NOK 5.2m

Financial health · 2024

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.9%
Good
Equity as a share of total capital

Who owns BAGLERBYEN FUS BARNEHAGE AS?

SFR BARNEHAGER AS
BAGLERBYEN FUS BARNEHAGE AS
NOK 17.6m rev. · NOK 951,000 profit

BAGLERBYEN FUS BARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BAGLERBYEN FUS BARNEHAGE AS er morselskap for 210 datterselskaper:

Frequently asked questions about BAGLERBYEN FUS BARNEHAGE AS

Who owns BAGLERBYEN FUS BARNEHAGE AS?

SFR BARNEHAGER AS is the largest registered owner, with 100.0%.

What is the revenue of BAGLERBYEN FUS BARNEHAGE AS?

BAGLERBYEN FUS BARNEHAGE AS had revenue of NOK 17.6m in 2024.

Where is BAGLERBYEN FUS BARNEHAGE AS based?

BAGLERBYEN FUS BARNEHAGE AS has its business address in Oslo.

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.