biztrac. BETA
COMPANY REGISTER PROFILE
920174388 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of civilian ships and boats

BOS POWER NORTH AS

Org. no. 920174388 Limited company (AS) Vågan Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 32.8m
Operating profit NOK 3.9m
Equity NOK 3.8m
Incorporated 2017
Share capital NOK 100,000

BOS POWER NORTH AS is registered as a limited company in Vågan, Nordland with organisation number 920174388. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Levere servicetjenester til MTU-installasjoner gjennom oppdrag formidlet av konsernet.”. The most recent filed accounts, for the 2025 financial year, show NOK 32.8m in revenue and NOK 3.9m in operating profit.

Former names: HERKULES INVEST 262 AS, BOSI SOGN 1 AS, BERTEL O. STEEN TEKNIKK NORD (BOSTEK NORD) AS, BERTEL O. STEEN POWER SOLUTIONS NORTH AS

Key figures · 2025

Revenue
NOK 32.8m
▲ +4 %
Operating profit
NOK 3.9m
▲ +350 %
Equity
NOK 3.8m
▲ +12 %
Est. value
NOK 14.3m

Financial health · 2025

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
33.2%
Very good
Return on total assets
Solidity
30.1%
Good
Equity as a share of total capital

Who owns BOS POWER NORTH AS?

BOS POWER NORTH AS
NOK 32.8m rev. · NOK 3.9m profit

BOS POWER NORTH AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOS POWER NORTH AS

Who owns BOS POWER NORTH AS?

BOS POWER NORWAY AS is the largest registered owner, with 51.0%.

What is the revenue of BOS POWER NORTH AS?

BOS POWER NORTH AS had revenue of NOK 32.8m in 2025.

Where is BOS POWER NORTH AS based?

BOS POWER NORTH AS has its business address in Svolvær.

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.