biztrac. BETA
COMPANY REGISTER PROFILE
961904900 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

CRANEMASTER AS

Org. no. 961904900 Limited company (AS) Bamble Incorporated 1991 Active
Revenue 2025 NOK 162.5m
Operating profit NOK 24.6m
Equity NOK 79.7m
Incorporated 1991
Employees 22
Share capital NOK 2.4m

CRANEMASTER AS is registered as a limited company in Bamble, Telemark with organisation number 961904900. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1991 and has 22 registered employees. Registered share capital is NOK 2.4m, divided into 600 shares. The company's stated purpose is: “Utvikling og produksjon av produkter og salg av disse og tjenester ellers. Prioritet på egne produkter basert på avansert teknologi for offshore, shipping og alm. industri.”. The most recent filed accounts, for the 2025 financial year, show NOK 162.5m in revenue and NOK 24.6m in operating profit.

Former names: ERNST-B JOHANSEN AS

Key figures · 2025

Revenue
NOK 162.5m
▲ +158 %
Operating profit
NOK 24.6m
▲ +312 %
Equity
NOK 79.7m
▲ +28 %
Est. value
NOK 163.4m

Financial health · 2025

Liquidity
4.75
Very good
Current assets ÷ current liabilities
Profitability
24.2%
Very good
Return on total assets
Solidity
83.6%
Very good
Equity as a share of total capital

Who owns CRANEMASTER AS?

CRANEMASTER AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about CRANEMASTER AS

Who owns CRANEMASTER AS?

CM HOLDING AS is the largest registered owner, with 43.2%.

What is the revenue of CRANEMASTER AS?

CRANEMASTER AS had revenue of NOK 162.5m in 2025.

Who is the general manager of CRANEMASTER AS?

Espen Boseth Johansen is registered as general manager of CRANEMASTER AS.

Where is CRANEMASTER AS based?

CRANEMASTER AS has its business address in Stathelle.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.