BIZTRAC BETA
Pre-primary education

SYMRAHAGEN AS

Org. no. 985134847 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −37,000
Equity NOK 645,000
Incorporated 2002
Employees 5
Share capital NOK 100,000

Signals

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

SYMRAHAGEN AS is registered as a limited company in Oslo, Oslo with organisation number 985134847. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2002 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverv, drift og forvaltning av faste eiendommer for barnehage. Barnehagen skal gi barn under opplæringspliktig alder gode utviklings- og aktivitetsmuligheter i nær forståelse og samarbeid med barnas hjem. Barnehagen skal hjelpe til med å gi barna en oppdragelse i samsvar med kristne grunnverdier.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −37,000
Equity
NOK 645,000
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
2.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.3%
Very good
Equity as a share of total capital

Who owns SYMRAHAGEN AS?

TORHILD LEIRVIK
SYMRAHAGEN AS
NOK 2.4m rev. · NOK −37,000 profit

SYMRAHAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYMRAHAGEN AS

Who owns SYMRAHAGEN AS?

TORHILD LEIRVIK is the largest registered owner, with 100.0%.

What is the revenue of SYMRAHAGEN AS?

SYMRAHAGEN AS had revenue of NOK 2.4m in 2025.

Where is SYMRAHAGEN AS based?

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