BIZTRAC BETA
Sound recording and music publishing activities

GJENKLANG STUDIO AS

Org. no. 929782941 Limited company (AS) Ålesund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 760,000
Equity NOK 460,000
Incorporated 2022
Employees 6
Share capital NOK 30,000

GJENKLANG STUDIO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 929782941. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg og produksjon av podkast, vodkast, webinar og andre audiovisuelle innholdsprodukter tilpasset forskjellige mediekanaler.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 760,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 760,000
Equity
NOK 460,000
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns GJENKLANG STUDIO AS?

JAN IVAR WOLSTAD
GJENKLANG STUDIO AS
NOK 3.1m rev. · NOK 760,000 profit

GJENKLANG STUDIO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJENKLANG STUDIO AS

Who owns GJENKLANG STUDIO AS?

JAN IVAR WOLSTAD is the largest registered owner, with 50.0%.

What is the revenue of GJENKLANG STUDIO AS?

GJENKLANG STUDIO AS had revenue of NOK 3.1m in 2025.

Who is the general manager of GJENKLANG STUDIO AS?

Jan Ivar Wolstad is registered as general manager of GJENKLANG STUDIO AS.

Where is GJENKLANG STUDIO AS based?

GJENKLANG STUDIO AS has its business address in Ålesund.

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.