BIZTRAC BETA
Repair and maintenance of machinery

BRUBAKKEN AS

Org. no. 930730556 Limited company (AS) Porsgrunn Incorporated 1974 Active
Ownership graph ↗
Revenue 2024 NOK 197.7m
Operating profit NOK 5.8m
Equity NOK 137.5m
Incorporated 1974
Employees 49
Share capital NOK 25.1m

BRUBAKKEN AS is registered as a limited company in Porsgrunn, Telemark with organisation number 930730556. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1974 and has 49 registered employees. Registered share capital is NOK 25.1m, divided into 1500 shares. The company's stated purpose is: “Utleie av transportmateriell og servicemaskiner med og uten bemaning, samt handel og agentur- virksomhet innenfor dette produktområdet.”. The most recent filed accounts, for the 2024 financial year, show NOK 197.7m in revenue and NOK 5.8m in operating profit.

Key figures · 2024

Revenue
NOK 197.7m
Operating profit
NOK 5.8m
Equity
NOK 137.5m
Est. value
NOK 108.6m

Financial health · 2025

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

Who owns BRUBAKKEN AS?

BRUBAKKEN HOLDING AS
BRUBAKKEN AS
NOK 197.7m rev. · NOK 5.8m profit

BRUBAKKEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRUBAKKEN AS own?

BRUBAKKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRUBAKKEN AS

Who owns BRUBAKKEN AS?

BRUBAKKEN HOLDING AS is the largest registered owner, with 73.7%.

What is the revenue of BRUBAKKEN AS?

BRUBAKKEN AS had revenue of NOK 197.7m in 2024.

Who is the general manager of BRUBAKKEN AS?

Anders Henni is registered as general manager of BRUBAKKEN AS.

Where is BRUBAKKEN AS based?

BRUBAKKEN AS has its business address in Porsgrunn.

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.