BIZTRAC BETA
COMPANY REGISTER PROFILE
918080104 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of charities which distribute means themselves

STIFTELSEN ØYVIND STRANDS MUSIKKFOND

Org. no. 918080104 Foundation (STI) Skien Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 136,000
Incorporated 2016
Share capital NOK 100,000

Signals

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

STIFTELSEN ØYVIND STRANDS MUSIKKFOND is registered as a foundation in Skien, Telemark with organisation number 918080104. The business is classified under activities of charities which distribute means themselves (NACE 94.991). The company was incorporated in 2016. Registered share capital is NOK 100,000.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 136,000
Est. value
NOK 180,000

Financial health · 2025

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

Who owns STIFTELSEN ØYVIND STRANDS MUSIKKFOND?

No shareholders are registered for STIFTELSEN ØYVIND STRANDS MUSIKKFOND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STIFTELSEN ØYVIND STRANDS MUSIKKFOND

Where is STIFTELSEN ØYVIND STRANDS MUSIKKFOND based?

STIFTELSEN ØYVIND STRANDS MUSIKKFOND has its business address in Skien.

Property

Business address Mælagata sør 25, 3716 Skien
Cadastral unit 4003-300/2994/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.