BIZTRAC BETA
Geological surveying

CRESSIDA AS

Org. no. 994010182 Limited company (AS) Kristiansand Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 19.0m
Operating profit NOK 18.1m
Equity NOK 179.5m
Incorporated 2009
Share capital NOK 100.0m

CRESSIDA AS is registered as a limited company in Kristiansand, Agder with organisation number 994010182. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2009. Registered share capital is NOK 100.0m, divided into 100000 shares. The company's stated purpose is: “Kjøpe, eie og selge aksjer, obligasjoner og andre finansielle instrumenter og alt som er beslektet eller står i forbindelse med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.0m in revenue and NOK 18.1m in operating profit.

Key figures · 2025

Revenue
NOK 19.0m
Operating profit
NOK 18.1m
Equity
NOK 179.5m
Est. value
NOK 160.6m

Financial health · 2025

Liquidity
2.19
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.3%
Very good
Equity as a share of total capital

Who owns CRESSIDA AS?

RASMUSSENGRUPPEN AS
CRESSIDA AS
NOK 19.0m rev. · NOK 18.1m profit

CRESSIDA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CRESSIDA AS own?

CRESSIDA AS holds stakes in 9 companies:

See the full ownership structure →

Group structure

CRESSIDA AS er morselskap for 36 datterselskaper:

Frequently asked questions about CRESSIDA AS

Who owns CRESSIDA AS?

RASMUSSENGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of CRESSIDA AS?

CRESSIDA AS had revenue of NOK 19.0m in 2025.

Who is the general manager of CRESSIDA AS?

Trygve Lauvdal is registered as general manager of CRESSIDA AS.

Where is CRESSIDA AS based?

CRESSIDA AS has its business address in Kristiansand S.

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.