biztrac. BETA
COMPANY REGISTER PROFILE
935265231 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Pre-primary education

GRID FUS BARNEHAGE AS

Org. no. 935265231 Limited company (AS) Haugesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

GRID FUS BARNEHAGE AS is registered as a limited company in Haugesund, Rogaland with organisation number 935265231. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å bygge, eie og drive barnehage av god kvalitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 23,000
Est. value
NOK 32,000

Financial health · 2025

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

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

Who owns GRID FUS BARNEHAGE AS?

GRID FUS BARNEHAGE AS
NOK 0 rev. · NOK −10,000 profit

GRID FUS BARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GRID FUS BARNEHAGE AS er morselskap for 210 datterselskaper:

Frequently asked questions about GRID FUS BARNEHAGE AS

Who owns GRID FUS BARNEHAGE AS?

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

What is the revenue of GRID FUS BARNEHAGE AS?

GRID FUS BARNEHAGE AS had revenue of NOK 0 in 2025.

Where is GRID FUS BARNEHAGE AS based?

GRID FUS BARNEHAGE AS has its business address in Haugesund.

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.