BIZTRAC BETA
Performing arts activities in music

EPIC LOOPS AS

Org. no. 922537798 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 164,000
Operating profit NOK −406,000
Equity NOK 63,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

EPIC LOOPS AS is registered as a limited company in Oslo, Oslo with organisation number 922537798. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Digitalt salg av musikk og lydfiler via egne nettbutikker til et verdensmarked av firmaer og innholdsprodusenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 164,000 in revenue and NOK −406,000 in operating profit.

Key figures · 2025

Revenue
NOK 164,000
Operating profit
NOK −406,000
Equity
NOK 63,000
Est. value
NOK 193,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns EPIC LOOPS AS?

OLE RICHARD KORSAN STUWE
EPIC LOOPS AS
NOK 164,000 rev. · NOK −406,000 profit

EPIC LOOPS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPIC LOOPS AS

Who owns EPIC LOOPS AS?

OLE RICHARD KORSAN STUWE is the largest registered owner, with 100.0%.

What is the revenue of EPIC LOOPS AS?

EPIC LOOPS AS had revenue of NOK 164,000 in 2025.

Who is the general manager of EPIC LOOPS AS?

Ole Richard Korsan Stuwe is registered as general manager of EPIC LOOPS AS.

Where is EPIC LOOPS AS based?

EPIC LOOPS 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.