biztrac. BETA
COMPANY REGISTER PROFILE
971558415 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other activities of other membership organisations

DANSEINFORMASJONEN STI

Org. no. 971558415 Foundation (STI) Oslo Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 8.4m
Operating profit NOK −614,000
Equity NOK 867,000
Incorporated 1994
Employees 5
Share capital NOK 250,000

Signals

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

DANSEINFORMASJONEN STI is registered as a foundation in Oslo, Oslo with organisation number 971558415. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1994 and has 5 registered employees. Registered share capital is NOK 250,000. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK −614,000 in operating profit.

Former names: SENTER FOR DANSEKUNST, STIFTELSEN SENTER FOR DANSEKUNST

Key figures · 2025

Revenue
NOK 8.4m
▲ +3 %
Operating profit
NOK −614,000
▼ −1624 %
Equity
NOK 867,000
▼ −35 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
-16.6%
Not satisfactory
Return on total assets
Solidity
31.1%
Good
Equity as a share of total capital

Who owns DANSEINFORMASJONEN STI?

No shareholders are registered for DANSEINFORMASJONEN STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about DANSEINFORMASJONEN STI

What is the revenue of DANSEINFORMASJONEN STI?

DANSEINFORMASJONEN STI had revenue of NOK 8.4m in 2025.

Who is the general manager of DANSEINFORMASJONEN STI?

Sanna Eriksson Ryg is registered as general manager of DANSEINFORMASJONEN STI.

Where is DANSEINFORMASJONEN STI based?

DANSEINFORMASJONEN STI has its business address in Oslo.

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.