BIZTRAC BETA
Development of building projects

CAVE LYNX AS

Org. no. 997420438 Limited company (AS) Bergen Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −201,000
Equity NOK −345,000
Incorporated 2011
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−345k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−201k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CAVE LYNX AS is registered as a limited company in Bergen, Vestland with organisation number 997420438. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp og salg av verdipapirer, industri og annen virksomhet, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −201,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −201,000
Equity
NOK −345,000

Financial health · 2024

Liquidity
3.72
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-45.7%
Weak
Equity as a share of total capital

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

Who owns CAVE LYNX AS?

MONTEM AS
CAVE LYNX AS
NOK 0 rev. · NOK −201,000 profit

CAVE LYNX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CAVE LYNX AS

Who owns CAVE LYNX AS?

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

What is the revenue of CAVE LYNX AS?

CAVE LYNX AS had revenue of NOK 0 in 2024.

Where is CAVE LYNX AS based?

CAVE LYNX AS has its business address in Bergen.

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.