BIZTRAC BETA
COMPANY REGISTER PROFILE
928990958 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Civil engineering activities

LYKKE HOME AS

Org. no. 928990958 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 15,000
Operating profit NOK 15,000
Equity NOK 46,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-10 Adresseendring registrert 2026-06-10.

LYKKE HOME AS is registered as a limited company in Oslo, Oslo with organisation number 928990958. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivning og konsulenttjenester innen bygg og anlegg.”. The most recent filed accounts, for the 2024 financial year, show NOK 15,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 15,000
Operating profit
NOK 15,000
Equity
NOK 46,000
Est. value
NOK 79,000

Financial health · 2024

Liquidity
8.04
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.6%
Weak
Equity as a share of total capital

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

Who owns LYKKE HOME AS?

LYKKE HOLDING AS
LYKKE HOME AS
NOK 15,000 rev. · NOK 15,000 profit

LYKKE HOME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYKKE HOME AS

Who owns LYKKE HOME AS?

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

What is the revenue of LYKKE HOME AS?

LYKKE HOME AS had revenue of NOK 15,000 in 2024.

Who is the general manager of LYKKE HOME AS?

Nikoletta Klaudia Jedrzejewska is registered as general manager of LYKKE HOME AS.

Where is LYKKE HOME AS based?

LYKKE HOME AS has its business address in Oslo.

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.