BIZTRAC BETA
Site preparation

JH BRUUN AS

Org. no. 991475303 Limited company (AS) Øvre Eiker Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 49,000
Operating profit NOK −28,000
Equity NOK 13,000
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

JH BRUUN AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 991475303. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Transportvirksomhet og alt som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 49,000 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 49,000
Operating profit
NOK −28,000
Equity
NOK 13,000
Est. value
NOK 22,000

Financial health · 2025

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
72.0%
Weak
Equity as a share of total capital

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

Who owns JH BRUUN AS?

JAN HENRIK BRUUN
JH BRUUN AS
NOK 49,000 rev. · NOK −28,000 profit

JH BRUUN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JH BRUUN AS own?

JH BRUUN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JH BRUUN AS

Who owns JH BRUUN AS?

JAN HENRIK BRUUN is the largest registered owner, with 50.0%.

What is the revenue of JH BRUUN AS?

JH BRUUN AS had revenue of NOK 49,000 in 2025.

Who is the general manager of JH BRUUN AS?

Jan Henrik Bruun is registered as general manager of JH BRUUN AS.

Where is JH BRUUN AS based?

JH BRUUN AS has its business address in Hokksund.

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.