BIZTRAC BETA
Development of building projects

CROSS MANAGEMENT AS

Org. no. 952137921 Limited company (AS) Bergen Incorporated 1989 Active
Ownership graph ↗
Operating profit NOK −1.6m
Equity NOK 70.3m
Incorporated 1989
Share capital NOK 107,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).
  • Nylig endring 2026-03-31 Aksjekapital registrert 2026-03-31.

CROSS MANAGEMENT AS is registered as a limited company in Bergen, Vestland with organisation number 952137921. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1989. Registered share capital is NOK 107,000, divided into 2133188 shares. The company's stated purpose is: “Besittelse og forvaltning av aksjer, eiendom og andre eiendeler, herunder aktiv og passiv deltagelse i andre selskaper, samt beslektede og tilstøtende aktiviteter i inn- og utland.”.

Key figures · 2024

Operating profit
NOK −1.6m
Equity
NOK 70.3m
Est. value
NOK 88.9m

Financial health · 2024

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.3%
Good
Equity as a share of total capital

Who owns CROSS MANAGEMENT AS?

KIM ANDRE ELTVIK KROSSØY
CROSS MANAGEMENT AS
· NOK −1.6m profit

CROSS MANAGEMENT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CROSS MANAGEMENT AS own?

CROSS MANAGEMENT AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about CROSS MANAGEMENT AS

Who owns CROSS MANAGEMENT AS?

KIM ANDRE ELTVIK KROSSØY is the largest registered owner, with 99.0%.

Who is the general manager of CROSS MANAGEMENT AS?

Hans Helge Krossøy is registered as general manager of CROSS MANAGEMENT AS.

Where is CROSS MANAGEMENT AS based?

CROSS MANAGEMENT AS has its business address in Paradis.

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.