BIZTRAC BETA
Pre-primary education

TUBUS BARNEHAGE AS

Org. no. 930679151 Limited company (AS) Sarpsborg Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 19.5m
Operating profit NOK 55,000
Equity NOK 3.3m
Incorporated 2022
Employees 33
Share capital NOK 30,000

Signals

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

TUBUS BARNEHAGE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 930679151. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2022 and has 33 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Barnehagedrift og alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.5m in revenue and NOK 55,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.5m
Operating profit
NOK 55,000
Equity
NOK 3.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns TUBUS BARNEHAGE AS?

NEDRE GLOMMEN HOLDING AS
TUBUS BARNEHAGE AS
NOK 19.5m rev. · NOK 55,000 profit

TUBUS BARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUBUS BARNEHAGE AS

Who owns TUBUS BARNEHAGE AS?

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

What is the revenue of TUBUS BARNEHAGE AS?

TUBUS BARNEHAGE AS had revenue of NOK 19.5m in 2024.

Who is the general manager of TUBUS BARNEHAGE AS?

Eirik Husby is registered as general manager of TUBUS BARNEHAGE AS.

Where is TUBUS BARNEHAGE AS based?

TUBUS BARNEHAGE AS has its business address in Sarpsborg.

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.