BIZTRAC BETA
Site preparation

E-18 HAGESENTER AS

Org. no. 828989162 Limited company (AS) Lillesand Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 55,000
Equity NOK 1.5m
Incorporated 2022
Share capital NOK 30,000

E-18 HAGESENTER AS is registered as a limited company in Lillesand, Agder with organisation number 828989162. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg av maskiner, hageprodukter og anleggsvirksomhet samt alt hva hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 55,000
Equity
NOK 1.5m
Est. value
NOK 794,000

Financial health · 2025

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

Who owns E-18 HAGESENTER AS?

LAUPSA HOLDING AS
E-18 HAGESENTER AS
NOK 1.3m rev. · NOK 55,000 profit

E-18 HAGESENTER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does E-18 HAGESENTER AS own?

E-18 HAGESENTER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about E-18 HAGESENTER AS

Who owns E-18 HAGESENTER AS?

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

What is the revenue of E-18 HAGESENTER AS?

E-18 HAGESENTER AS had revenue of NOK 1.3m in 2025.

Who is the general manager of E-18 HAGESENTER AS?

Alf Laupsa is registered as general manager of E-18 HAGESENTER AS.

Where is E-18 HAGESENTER AS based?

E-18 HAGESENTER AS has its business address in Lillesand.

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.