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

BSI OFFSHORE AS

Org. no. 896310682 Limited company (AS) Bergen Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 64.9m
Operating profit NOK 1.5m
Equity NOK 6.7m
Incorporated 2010
Employees 40
Share capital NOK 100,000

BSI OFFSHORE AS is registered as a limited company in Bergen, Vestland with organisation number 896310682. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2010 and has 40 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Virksomhet innen skips- og offshoreinnredning og isolering, samt leveranser av relaterte produkter og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 64.9m in revenue and NOK 1.5m in operating profit.

Former names: KOLBEINSVARDEN AS

Key figures · 2025

Revenue
NOK 64.9m
▼ −24 %
Operating profit
NOK 1.5m
▼ −79 %
Equity
NOK 6.7m
▲ +7 %
Est. value
NOK 14.1m

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
7.2%
Satisfactory
Return on total assets
Solidity
29.9%
Good
Equity as a share of total capital

Who owns BSI OFFSHORE AS?

BSI OFFSHORE AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about BSI OFFSHORE AS

Who owns BSI OFFSHORE AS?

KOLBEINSVARDEN AS is the largest registered owner, with 97.0%.

What is the revenue of BSI OFFSHORE AS?

BSI OFFSHORE AS had revenue of NOK 64.9m in 2025.

Who is the general manager of BSI OFFSHORE AS?

Audun Lokøy is registered as general manager of BSI OFFSHORE AS.

Where is BSI OFFSHORE AS based?

BSI OFFSHORE AS has its business address in Laksevåg.

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.