biztrac. BETA
COMPANY REGISTER PROFILE
922126844 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Landscape service activities

LYKKEHAVEN AS

Org. no. 922126844 Limited company (AS) Gjerdrum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 840,000
Operating profit NOK 4,000
Equity NOK 62,000
Incorporated 2019
Share capital NOK 30,000

LYKKEHAVEN AS is registered as a limited company in Gjerdrum, Akershus with organisation number 922126844. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby tjenester innen felter som økologi, gartner m.m. og annet som naturlig faler sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 840,000 in revenue and NOK 4,000 in operating profit.

Former names: LOVE ELIDA AS

Key figures · 2025

Revenue
NOK 840,000
▼ −62 %
Operating profit
NOK 4,000
▼ −39 %
Equity
NOK 62,000
▼ −8 %
Est. value
NOK 55,000

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
26.1%
Weak
Equity as a share of total capital

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

Who owns LYKKEHAVEN AS?

LYKKEHAVEN AS
NOK 840,000 rev. · NOK 4,000 profit

LYKKEHAVEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYKKEHAVEN AS

Who owns LYKKEHAVEN AS?

Elida Smestad is the largest registered owner, with 100.0%.

What is the revenue of LYKKEHAVEN AS?

LYKKEHAVEN AS had revenue of NOK 840,000 in 2025.

Who is the general manager of LYKKEHAVEN AS?

Elida Smestad is registered as general manager of LYKKEHAVEN AS.

Where is LYKKEHAVEN AS based?

LYKKEHAVEN AS has its business address in Gjerdrum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.