BIZTRAC BETA
Joinery installation

JAN ERIK BRENNE AS

Org. no. 913099745 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 44,000
Equity NOK 1.0m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-13 Adresseendring registrert 2026-04-13.

JAN ERIK BRENNE AS is registered as a limited company in Bærum, Akershus with organisation number 913099745. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Levere bygg og håndverkstjenester, totalentrepriser og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 44,000
Equity
NOK 1.0m
Est. value
NOK 639,000

Financial health · 2025

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

Who owns JAN ERIK BRENNE AS?

JAN-ERIK HASSELHOFF BRENNE
JAN ERIK BRENNE AS
NOK 3.8m rev. · NOK 44,000 profit

JAN ERIK BRENNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAN ERIK BRENNE AS

Who owns JAN ERIK BRENNE AS?

JAN-ERIK HASSELHOFF BRENNE is the largest registered owner, with 100.0%.

What is the revenue of JAN ERIK BRENNE AS?

JAN ERIK BRENNE AS had revenue of NOK 3.8m in 2025.

Who is the general manager of JAN ERIK BRENNE AS?

Jan-Erik Hasselhoff Brenne is registered as general manager of JAN ERIK BRENNE AS.

Where is JAN ERIK BRENNE AS based?

JAN ERIK BRENNE AS has its business address in Jar.

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.