BIZTRAC BETA
COMPANY REGISTER PROFILE
997085604 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Activities of tourist offices and destination marketing organisations

FORENINGEN CRUISE SØRLANDET

Org. no. 997085604 Association/club/organisation (FLI) Kristiansand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK −830,000
Equity NOK 324,000
Incorporated 2011

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−830k kr).

FORENINGEN CRUISE SØRLANDET is registered as a association/club/organisation in Kristiansand, Agder with organisation number 997085604. The business is classified under activities of tourist offices and destination marketing organisations (NACE 79.901). The company was incorporated in 2011. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK −830,000 in operating profit.

Former names: CRUISE KRISTIANSAND, CRUISE SØRLANDET

Key figures · 2025

Revenue
NOK 7.9m
Operating profit
NOK −830,000
Equity
NOK 324,000
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns FORENINGEN CRUISE SØRLANDET?

No shareholders are registered for FORENINGEN CRUISE SØRLANDET in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FORENINGEN CRUISE SØRLANDET

What is the revenue of FORENINGEN CRUISE SØRLANDET?

FORENINGEN CRUISE SØRLANDET had revenue of NOK 7.9m in 2025.

Who is the general manager of FORENINGEN CRUISE SØRLANDET?

Marianne Pedersen is registered as general manager of FORENINGEN CRUISE SØRLANDET.

Where is FORENINGEN CRUISE SØRLANDET based?

FORENINGEN CRUISE SØRLANDET 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 02.09.2026.

Report a problem

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