biztrac. BETA
COMPANY REGISTER PROFILE
988113107 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
General secondary education

STIFTELSEN TELEMARK TOPPIDRETT GYMNAS

Org. no. 988113107 Foundation (STI) Skien Incorporated 2005 Active
Revenue 2025 NOK 60.6m
Operating profit NOK 3.7m
Equity NOK 10.5m
Incorporated 2005
Employees 62
Share capital NOK 200,000

STIFTELSEN TELEMARK TOPPIDRETT GYMNAS is registered as a foundation in Skien, Telemark with organisation number 988113107. The business is classified under general secondary education (NACE 85.310). The company was incorporated in 2005 and has 62 registered employees. Registered share capital is NOK 200,000. The most recent filed accounts, for the 2025 financial year, show NOK 60.6m in revenue and NOK 3.7m in operating profit.

Former names: STIFTELSEN TOPPIDRETTSGYMNASET I TELEMARK

Key figures · 2025

Revenue
NOK 60.6m
▲ +12 %
Operating profit
NOK 3.7m
▲ +104 %
Equity
NOK 10.5m
▲ +59 %
Est. value
NOK 21.2m

Financial health · 2025

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
22.3%
Very good
Return on total assets
Solidity
54.1%
Very good
Equity as a share of total capital

Who owns STIFTELSEN TELEMARK TOPPIDRETT GYMNAS?

No shareholders are registered for STIFTELSEN TELEMARK TOPPIDRETT GYMNAS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN TELEMARK TOPPIDRETT GYMNAS

What is the revenue of STIFTELSEN TELEMARK TOPPIDRETT GYMNAS?

STIFTELSEN TELEMARK TOPPIDRETT GYMNAS had revenue of NOK 60.6m in 2025.

Who is the general manager of STIFTELSEN TELEMARK TOPPIDRETT GYMNAS?

Alv Øystese is registered as general manager of STIFTELSEN TELEMARK TOPPIDRETT GYMNAS.

Where is STIFTELSEN TELEMARK TOPPIDRETT GYMNAS based?

STIFTELSEN TELEMARK TOPPIDRETT GYMNAS has its business address in Skien.

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.