biztrac. BETA
COMPANY REGISTER PROFILE
929001761 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sound recording and music publishing activities

LOKI LYDSTUDIO AS

Org. no. 929001761 Limited company (AS) Bergen Incorporated 2022 Active
Revenue 2025 NOK 610,000
Operating profit NOK −4,000
Equity NOK 33,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

LOKI LYDSTUDIO AS is registered as a limited company in Bergen, Vestland with organisation number 929001761. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drift av lydstudio. Vi tilbyr lydproduksjonstjenester som innspilling av lyd, miksing, mastering, komponering og arrangering.”. The most recent filed accounts, for the 2025 financial year, show NOK 610,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 610,000
▲ +7 %
Operating profit
NOK −4,000
▼ −129 %
Equity
NOK 33,000
▼ −6 %
Est. value
NOK 48,000

Financial health · 2025

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

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

Who owns LOKI LYDSTUDIO AS?

LOKI LYDSTUDIO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOKI LYDSTUDIO AS

Who owns LOKI LYDSTUDIO AS?

Charles David Wise is the largest registered owner, with 33.3%.

What is the revenue of LOKI LYDSTUDIO AS?

LOKI LYDSTUDIO AS had revenue of NOK 610,000 in 2025.

Where is LOKI LYDSTUDIO AS based?

LOKI LYDSTUDIO AS has its business address in Bergen.

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.