BIZTRAC BETA
Arts creation activities in literature

HEAVY BOOKS AS

Org. no. 931754815 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 155,000
Operating profit NOK −55,000
Equity NOK −31,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−31k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−55k kr).

HEAVY BOOKS AS is registered as a limited company in Asker, Akershus with organisation number 931754815. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kunstkonsulent, design av bøker, salg av kunst på vegne av kunstnere.”. The most recent filed accounts, for the 2024 financial year, show NOK 155,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2024

Revenue
NOK 155,000
Operating profit
NOK −55,000
Equity
NOK −31,000

Financial health · 2024

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

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

Who owns HEAVY BOOKS AS?

CHRISTIAN TUNGE
HEAVY BOOKS AS
NOK 155,000 rev. · NOK −55,000 profit

HEAVY BOOKS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEAVY BOOKS AS

Who owns HEAVY BOOKS AS?

CHRISTIAN TUNGE is the largest registered owner, with 100.0%.

What is the revenue of HEAVY BOOKS AS?

HEAVY BOOKS AS had revenue of NOK 155,000 in 2024.

Who is the general manager of HEAVY BOOKS AS?

Christian Tunge is registered as general manager of HEAVY BOOKS AS.

Where is HEAVY BOOKS AS based?

HEAVY BOOKS AS has its business address in Heggedal.

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.