biztrac. BETA
COMPANY REGISTER PROFILE
913990285 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Performing arts activities in music

OSLO STRINGS SAMVIRKEFORETAK

Org. no. 913990285 Co-operation (SA) Oslo Incorporated 2014 Active
Revenue 2025 NOK 984,000
Operating profit NOK −24,000
Equity NOK −90,000
Incorporated 2014

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−90k kr).

OSLO STRINGS SAMVIRKEFORETAK is registered as a co-operation in Oslo, Oslo with organisation number 913990285. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2014. The company's stated purpose is: “Utøvende musikk, og alt hva herved er i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 984,000 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 984,000
▲ +44 %
Operating profit
NOK −24,000
▼ −340 %
Equity
NOK −90,000
▼ −36 %
Est. value
NOK 2,000

Financial health · 2025

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
-17.7%
Not satisfactory
Return on total assets
Solidity
-62.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OSLO STRINGS SAMVIRKEFORETAK?

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

Frequently asked questions about OSLO STRINGS SAMVIRKEFORETAK

What is the revenue of OSLO STRINGS SAMVIRKEFORETAK?

OSLO STRINGS SAMVIRKEFORETAK had revenue of NOK 984,000 in 2025.

Who is the general manager of OSLO STRINGS SAMVIRKEFORETAK?

Kaja Fjellberg Pettersen is registered as general manager of OSLO STRINGS SAMVIRKEFORETAK.

Where is OSLO STRINGS SAMVIRKEFORETAK based?

OSLO STRINGS SAMVIRKEFORETAK 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.