BIZTRAC BETA
Sound recording and music publishing activities

COMMON KNOWLEDGE AS

Org. no. 925832235 Limited company (AS) Frogn Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 774,000
Equity NOK 390,000
Incorporated 2020
Share capital NOK 30,000

COMMON KNOWLEDGE AS is registered as a limited company in Frogn, Akershus with organisation number 925832235. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bredt anlagt musikkselskap som tilbyr produksjon og utgivelse av lydopptak, publisering, rådgivning, management, PR, booking, investeringer i copyrights. Delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 774,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 774,000
Equity
NOK 390,000
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns COMMON KNOWLEDGE AS?

TWENTY TEN MANAGEMENT AS
COMMON KNOWLEDGE AS
NOK 1.9m rev. · NOK 774,000 profit

COMMON KNOWLEDGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COMMON KNOWLEDGE AS

Who owns COMMON KNOWLEDGE AS?

TWENTY TEN MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of COMMON KNOWLEDGE AS?

COMMON KNOWLEDGE AS had revenue of NOK 1.9m in 2024.

Where is COMMON KNOWLEDGE AS based?

COMMON KNOWLEDGE AS has its business address in Drøbak.

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.