biztrac. BETA
COMPANY REGISTER PROFILE
912066878 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other support activities for petroleum and natural gas extraction

GEO CASPIAN OPERATION AS

Org. no. 912066878 Limited company (AS) Herøy Incorporated 2013 Active
Operating profit NOK −155,000
Equity NOK −16.4m
Incorporated 2013
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−16,4 mill kr).

GEO CASPIAN OPERATION AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 912066878. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Drive offshore fartøyer og/eller, direkte eller som medeier eller deltaker, å foreta investeringer i skipsfart og andre maritime næringer.”.

Key figures · 2025

Operating profit
NOK −155,000
▲ +70 %
Equity
NOK −16.4m
▼ −30 %

Financial health · 2025

Liquidity
203.19
Very good
Current assets ÷ current liabilities
Profitability
-2.1%
Not satisfactory
Return on total assets
Solidity
-288.6%
Weak
Equity as a share of total capital

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

Who owns GEO CASPIAN OPERATION AS?

GEO CASPIAN OPERATION AS
· NOK −155,000 profit

GEO CASPIAN OPERATION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GEO CASPIAN OPERATION AS

Who owns GEO CASPIAN OPERATION AS?

GEO CASPIAN AS is the largest registered owner, with 100.0%.

Who is the general manager of GEO CASPIAN OPERATION AS?

Christoffer Syversen is registered as general manager of GEO CASPIAN OPERATION AS.

Where is GEO CASPIAN OPERATION AS based?

GEO CASPIAN OPERATION AS has its business address in Fosnavå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.