BIZTRAC BETA
Retail sale of books

C R BERGES BOKHANDEL AS

Org. no. 983638198 Limited company (AS) Kristiansand Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 347,000
Equity NOK 5.1m
Incorporated 2001
Employees 17
Share capital NOK 1.2m

C R BERGES BOKHANDEL AS is registered as a limited company in Kristiansand, Agder with organisation number 983638198. The business is classified under retail sale of books (NACE 47.610). The company was incorporated in 2001 and has 17 registered employees. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift og/eller leie av bokhandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 347,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
Operating profit
NOK 347,000
Equity
NOK 5.1m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns C R BERGES BOKHANDEL AS?

TORE MARTINSEN
C R BERGES BOKHANDEL AS
NOK 12.9m rev. · NOK 347,000 profit

C R BERGES BOKHANDEL AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about C R BERGES BOKHANDEL AS

Who owns C R BERGES BOKHANDEL AS?

TORE MARTINSEN is the largest registered owner, with 50.0%.

What is the revenue of C R BERGES BOKHANDEL AS?

C R BERGES BOKHANDEL AS had revenue of NOK 12.9m in 2025.

Who is the general manager of C R BERGES BOKHANDEL AS?

Lars Erling Myrvold is registered as general manager of C R BERGES BOKHANDEL AS.

Where is C R BERGES BOKHANDEL AS based?

C R BERGES BOKHANDEL AS has its business address in Kristiansand S.

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.