BIZTRAC BETA
Sound recording and music publishing activities

STRENGELEIK AS

Org. no. 833580922 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 461,000
Operating profit NOK 300,000
Equity NOK 164,000
Incorporated 2024
Share capital NOK 30,000

STRENGELEIK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 833580922. 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 30 shares. The company's stated purpose is: “Selskapets virksomhet er spilleoppdrag, musikkproduksjon og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 461,000 in revenue and NOK 300,000 in operating profit.

Key figures · 2024

Revenue
NOK 461,000
Operating profit
NOK 300,000
Equity
NOK 164,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns STRENGELEIK AS?

SKJALG MIKALSEN RAAEN
STRENGELEIK AS
NOK 461,000 rev. · NOK 300,000 profit

STRENGELEIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRENGELEIK AS

Who owns STRENGELEIK AS?

SKJALG MIKALSEN RAAEN is the largest registered owner, with 100.0%.

What is the revenue of STRENGELEIK AS?

STRENGELEIK AS had revenue of NOK 461,000 in 2024.

Where is STRENGELEIK AS based?

STRENGELEIK AS has its business address in Ranheim.

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.