BIZTRAC BETA
Pre-primary education

SMEDBAKKEN FUS BARNEHAGE AS

Org. no. 922030499 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 14.4m
Operating profit NOK 61,000
Equity NOK 854,000
Incorporated 2018
Employees 18
Share capital NOK 200,000

SMEDBAKKEN FUS BARNEHAGE AS is registered as a limited company in Oslo, Oslo with organisation number 922030499. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2018 and has 18 registered employees. Registered share capital is NOK 200,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 14.4m in revenue and NOK 61,000 in operating profit.

Key figures · 2024

Revenue
NOK 14.4m
Operating profit
NOK 61,000
Equity
NOK 854,000
Est. value
NOK 784,000

Financial health · 2024

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

Who owns SMEDBAKKEN FUS BARNEHAGE AS?

SFR BARNEHAGER AS
SMEDBAKKEN FUS BARNEHAGE AS
NOK 14.4m rev. · NOK 61,000 profit

SMEDBAKKEN FUS BARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SMEDBAKKEN FUS BARNEHAGE AS er morselskap for 210 datterselskaper:

Frequently asked questions about SMEDBAKKEN FUS BARNEHAGE AS

Who owns SMEDBAKKEN FUS BARNEHAGE AS?

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

What is the revenue of SMEDBAKKEN FUS BARNEHAGE AS?

SMEDBAKKEN FUS BARNEHAGE AS had revenue of NOK 14.4m in 2024.

Who is the general manager of SMEDBAKKEN FUS BARNEHAGE AS?

Tina Weckhorst is registered as general manager of SMEDBAKKEN FUS BARNEHAGE AS.

Where is SMEDBAKKEN FUS BARNEHAGE AS based?

SMEDBAKKEN 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.