BIZTRAC BETA
Uoppgitt

SHEARWATER GEOSERVICES ASSETS VIII AS

Org. no. 932256126 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −3.7m
Equity NOK −7.9m
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−7,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,7 mill kr).

SHEARWATER GEOSERVICES ASSETS VIII AS is registered as a limited company in Bergen, Vestland with organisation number 932256126. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Direkte eller indirekte drift og eierskap av skip med tilhørende aktiviteter, samt hva hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −3.7m
Equity
NOK −7.9m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-20.9%
Weak
Equity as a share of total capital

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

Who owns SHEARWATER GEOSERVICES ASSETS VIII AS?

SHEARWATER INVEST AS
SHEARWATER GEOSERVICES ASSETS VIII AS
· NOK −3.7m profit

SHEARWATER GEOSERVICES ASSETS VIII AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHEARWATER GEOSERVICES ASSETS VIII AS

Who owns SHEARWATER GEOSERVICES ASSETS VIII AS?

SHEARWATER INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of SHEARWATER GEOSERVICES ASSETS VIII AS?

Irene Waage Basili is registered as general manager of SHEARWATER GEOSERVICES ASSETS VIII AS.

Where is SHEARWATER GEOSERVICES ASSETS VIII AS based?

SHEARWATER GEOSERVICES ASSETS VIII 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 15.06.2026.

Report a problem

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