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

BAKLENGS SALTO AS

Org. no. 929327403 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 136,000
Operating profit NOK −10,000
Equity NOK 41,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BAKLENGS SALTO AS is registered as a limited company in Oslo, Oslo with organisation number 929327403. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive kreativ musikalsk virksomhet, herunder fremføring, låtskriving og utgivelse av musikkverk, samt rettigheter og inntekter fra slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 136,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 136,000
▲ +86 %
Operating profit
NOK −10,000
▼ −126 %
Equity
NOK 41,000
▼ −20 %
Est. value
NOK 23,000

Financial health · 2025

Liquidity
14.36
Very good
Current assets ÷ current liabilities
Profitability
-14.6%
Not satisfactory
Return on total assets
Solidity
67.6%
Weak
Equity as a share of total capital

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

Who owns BAKLENGS SALTO AS?

BAKLENGS SALTO AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BAKLENGS SALTO AS

Who owns BAKLENGS SALTO AS?

Oskar Guthushagen is the largest registered owner, with 20.0%.

What is the revenue of BAKLENGS SALTO AS?

BAKLENGS SALTO AS had revenue of NOK 136,000 in 2025.

Where is BAKLENGS SALTO AS based?

BAKLENGS SALTO AS 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.