BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

CRISCO SUBSEA AS

Org. no. 932367912 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 3.1m
Equity NOK 36,000
Incorporated 2023
Share capital NOK 30,000

CRISCO SUBSEA AS is registered as a limited company in Stavanger, Rogaland with organisation number 932367912. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen olje og gass samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 3.1m
Equity
NOK 36,000
Est. value
NOK 9.0m

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.0%
Weak
Equity as a share of total capital

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

Who owns CRISCO SUBSEA AS?

SCOTT CHRISTOFFERSEN WOOD
CRISCO SUBSEA AS
NOK 4.6m rev. · NOK 3.1m profit

CRISCO SUBSEA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CRISCO SUBSEA AS

Who owns CRISCO SUBSEA AS?

SCOTT CHRISTOFFERSEN WOOD is the largest registered owner, with 100.0%.

What is the revenue of CRISCO SUBSEA AS?

CRISCO SUBSEA AS had revenue of NOK 4.6m in 2024.

Who is the general manager of CRISCO SUBSEA AS?

Scott Christoffersen Wood is registered as general manager of CRISCO SUBSEA AS.

Where is CRISCO SUBSEA AS based?

CRISCO SUBSEA AS has its business address in Stavanger.

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.