BIZTRAC BETA
Sound recording and music publishing activities

DUPER POST PUNKS AS

Org. no. 928775275 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 199,000
Equity NOK 164,000
Incorporated 2022
Share capital NOK 30,000

DUPER POST PUNKS AS is registered as a limited company in Bergen, Vestland with organisation number 928775275. 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 300 shares. The company's stated purpose is: “Å drive med lydetterarbeid og lyddesign til audiovisuelle produksjoner. Selskapet kan også engasjere seg i andre foretak uansett formål og selskapsform.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 199,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 199,000
Equity
NOK 164,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns DUPER POST PUNKS AS?

JORUNN BØRVE ERIKSEN
DUPER POST PUNKS AS
NOK 2.9m rev. · NOK 199,000 profit

DUPER POST PUNKS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DUPER POST PUNKS AS

Who owns DUPER POST PUNKS AS?

JORUNN BØRVE ERIKSEN is the largest registered owner, with 33.3%.

What is the revenue of DUPER POST PUNKS AS?

DUPER POST PUNKS AS had revenue of NOK 2.9m in 2024.

Who is the general manager of DUPER POST PUNKS AS?

Thomas Angell Endresen is registered as general manager of DUPER POST PUNKS AS.

Where is DUPER POST PUNKS AS based?

DUPER POST PUNKS 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 15.06.2026.

Report a problem

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