BIZTRAC BETA
Sound recording and music publishing activities

K59 BLOKK AS

Org. no. 933149528 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 241,000
Operating profit NOK −39,000
Equity NOK 121,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

K59 BLOKK AS is registered as a limited company in Oslo, Oslo with organisation number 933149528. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utgivelse av musikk og lyd og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 241,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2025

Revenue
NOK 241,000
Operating profit
NOK −39,000
Equity
NOK 121,000
Est. value
NOK 462,000

Financial health · 2025

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

Who owns K59 BLOKK AS?

MARIUS GALETIC
K59 BLOKK AS
NOK 241,000 rev. · NOK −39,000 profit

K59 BLOKK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about K59 BLOKK AS

Who owns K59 BLOKK AS?

MARIUS GALETIC is the largest registered owner, with 33.3%.

What is the revenue of K59 BLOKK AS?

K59 BLOKK AS had revenue of NOK 241,000 in 2025.

Who is the general manager of K59 BLOKK AS?

Thanujan Nageswaran is registered as general manager of K59 BLOKK AS.

Where is K59 BLOKK AS based?

K59 BLOKK 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.