BIZTRAC BETA
COMPANY REGISTER PROFILE
976281586 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of excursion and event organisers

SAGENE SKOLES MUSIKKORPS

Org. no. 976281586 Association/club/organisation (FLI) Oslo Incorporated 1905 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 129,000
Equity NOK 796,000
Incorporated 1905

SAGENE SKOLES MUSIKKORPS is registered as a association/club/organisation in Oslo, Oslo with organisation number 976281586. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 1905. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 129,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 129,000
Equity
NOK 796,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns SAGENE SKOLES MUSIKKORPS?

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

Frequently asked questions about SAGENE SKOLES MUSIKKORPS

What is the revenue of SAGENE SKOLES MUSIKKORPS?

SAGENE SKOLES MUSIKKORPS had revenue of NOK 1.4m in 2025.

Where is SAGENE SKOLES MUSIKKORPS based?

SAGENE SKOLES MUSIKKORPS has its business address in Oslo.

Property

Business address Biermanns gate 2, 0473 Oslo
Cadastral unit 301-225/35/0/0

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.