BIZTRAC BETA
COMPANY REGISTER PROFILE
989568116 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Vocational secondary education

STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE

Org. no. 989568116 Foundation (STI) Halden Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 24.1m
Operating profit NOK 1.2m
Equity NOK 21.7m
Incorporated 2005
Employees 25
Share capital NOK 100,000

STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE is registered as a foundation in Halden, Østfold with organisation number 989568116. The business is classified under vocational secondary education (NACE 85.320). The company was incorporated in 2005 and has 25 registered employees. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 24.1m in revenue and NOK 1.2m in operating profit.

Former names: STIFTELSEN HOPEN VIDEREGÅENDE SKOLE

Key figures · 2025

Revenue
NOK 24.1m
Operating profit
NOK 1.2m
Equity
NOK 21.7m
Est. value
NOK 20.6m

Financial health · 2025

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

Who owns STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE?

No shareholders are registered for STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE

What is the revenue of STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE?

STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE had revenue of NOK 24.1m in 2025.

Who is the general manager of STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE?

Bjørn Håvard Røyndal is registered as general manager of STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE.

Where is STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE based?

STIFTELSEN ØSTERBO VIDEREGÅENDE SKOLE has its business address in Halden.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.