BIZTRAC BETA
Development of building projects

LIAKROKEN TERRASSE AS

Org. no. 915864961 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK −16.1m
Incorporated 2015
Share capital NOK 14.7m

Signals

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

LIAKROKEN TERRASSE AS is registered as a limited company in Bergen, Vestland with organisation number 915864961. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 14.7m, divided into 14730000 shares. The company's stated purpose is: “Utvikle eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK −16.1m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-157.6%
Weak
Equity as a share of total capital

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

Who owns LIAKROKEN TERRASSE AS?

ALVERGRUPPEN AS
LIAKROKEN TERRASSE AS
NOK 0 rev. · NOK −5,000 profit

LIAKROKEN TERRASSE AS has 15 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIAKROKEN TERRASSE AS

Who owns LIAKROKEN TERRASSE AS?

ALVERGRUPPEN AS is the largest registered owner, with 60.0%.

What is the revenue of LIAKROKEN TERRASSE AS?

LIAKROKEN TERRASSE AS had revenue of NOK 0 in 2024.

Where is LIAKROKEN TERRASSE AS based?

LIAKROKEN TERRASSE 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.