BIZTRAC BETA
Rental and operating of own or leased real estate

LIER GARTNERIER AS

Org. no. 815488482 Limited company (AS) Lier Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −20,000
Equity NOK −15,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

LIER GARTNERIER AS is registered as a limited company in Lier, Buskerud with organisation number 815488482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie, utvikle og drive gartnerier, samt alt som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −20,000
Equity
NOK −15,000

Financial health · 2025

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

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

Who owns LIER GARTNERIER AS?

VIVELSTAD HOLDING AS
LIER GARTNERIER AS
· NOK −20,000 profit

LIER GARTNERIER AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LIER GARTNERIER AS er morselskap for 5 datterselskaper:

Frequently asked questions about LIER GARTNERIER AS

Who owns LIER GARTNERIER AS?

VIVELSTAD HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of LIER GARTNERIER AS?

Espen Gausen is registered as general manager of LIER GARTNERIER AS.

Where is LIER GARTNERIER AS based?

LIER GARTNERIER AS has its business address in Lier.

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.