BIZTRAC BETA
Pre-primary education

ÅSEBØEN NYBYGGBARNEHAGE AS

Org. no. 992337176 Limited company (AS) Karmøy Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK −2.1m
Incorporated 2008
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).

ÅSEBØEN NYBYGGBARNEHAGE AS is registered as a limited company in Karmøy, Rogaland with organisation number 992337176. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Barnehage.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −2.1m

Financial health · 2024

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

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

Who owns ÅSEBØEN NYBYGGBARNEHAGE AS?

SFR HOLDING AS
ÅSEBØEN NYBYGGBARNEHAGE AS
NOK 0 rev. · NOK −18,000 profit

ÅSEBØEN NYBYGGBARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ÅSEBØEN NYBYGGBARNEHAGE AS er morselskap for 210 datterselskaper:

Frequently asked questions about ÅSEBØEN NYBYGGBARNEHAGE AS

Who owns ÅSEBØEN NYBYGGBARNEHAGE AS?

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

What is the revenue of ÅSEBØEN NYBYGGBARNEHAGE AS?

ÅSEBØEN NYBYGGBARNEHAGE AS had revenue of NOK 0 in 2024.

Where is ÅSEBØEN NYBYGGBARNEHAGE AS based?

ÅSEBØEN NYBYGGBARNEHAGE AS has its business address in Kopervik.

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.