BIZTRAC BETA
Retail sale of furniture, including mattresses and box springs

JENS CHR BERLE AS

Org. no. 963261535 Limited company (AS) Bergen Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 28.1m
Operating profit NOK −2.1m
Equity NOK 9.9m
Incorporated 1992
Employees 9
Share capital NOK 36,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,1 mill kr).

JENS CHR BERLE AS is registered as a limited company in Bergen, Vestland with organisation number 963261535. The business is classified under retail sale of furniture, including mattresses and box springs (NACE 47.551). The company was incorporated in 1992 and has 9 registered employees. Registered share capital is NOK 36,000, divided into 100 shares. The company's stated purpose is: “Handelsvirksomhet og hva hermed er forbundet.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.1m in revenue and NOK −2.1m in operating profit.

Key figures · 2024

Revenue
NOK 28.1m
Operating profit
NOK −2.1m
Equity
NOK 9.9m
Est. value
NOK 13.8m

Financial health · 2024

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

Who owns JENS CHR BERLE AS?

GODE ROM AS
JENS CHR BERLE AS
NOK 28.1m rev. · NOK −2.1m profit

JENS CHR BERLE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JENS CHR BERLE AS

Who owns JENS CHR BERLE AS?

GODE ROM AS is the largest registered owner, with 96.0%.

What is the revenue of JENS CHR BERLE AS?

JENS CHR BERLE AS had revenue of NOK 28.1m in 2024.

Who is the general manager of JENS CHR BERLE AS?

Jens Christian Berle is registered as general manager of JENS CHR BERLE AS.

Where is JENS CHR BERLE AS based?

JENS CHR BERLE 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.