BIZTRAC BETA
General cleaning of buildings

LYKKE HJEMME AS

Org. no. 925897914 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 19.6m
Operating profit NOK 1.7m
Equity NOK 897,000
Incorporated 2020
Employees 48
Share capital NOK 780,000

LYKKE HJEMME AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925897914. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2020 and has 48 registered employees. Registered share capital is NOK 780,000, divided into 100 shares. The company's stated purpose is: “Renholdsvirksomhet for private hjem, samt små og mellomstore bedrifter, og andre tjenester og produkter som kommer inn under dette. Bedriften tilbyr personlig tjenesteyting og omsorgs service. Kjøp og salg av produkter, og utleie/kjøp av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.6m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 19.6m
Operating profit
NOK 1.7m
Equity
NOK 897,000
Est. value
NOK 7.0m

Financial health · 2024

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

Who owns LYKKE HJEMME AS?

HLT HOLDING AS
LYKKE HJEMME AS
NOK 19.6m rev. · NOK 1.7m profit

LYKKE HJEMME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYKKE HJEMME AS

Who owns LYKKE HJEMME AS?

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

What is the revenue of LYKKE HJEMME AS?

LYKKE HJEMME AS had revenue of NOK 19.6m in 2024.

Who is the general manager of LYKKE HJEMME AS?

Marius Aasen is registered as general manager of LYKKE HJEMME AS.

Where is LYKKE HJEMME AS based?

LYKKE HJEMME AS has its business address in Trondheim.

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.