BIZTRAC BETA
Manufacture of outerwear

LYKKE OG LITEN AS

Org. no. 924040424 Limited company (AS) Haugesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 98,000
Operating profit NOK −47,000
Equity NOK −22,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−22k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−47k kr).

LYKKE OG LITEN AS is registered as a limited company in Haugesund, Rogaland with organisation number 924040424. The business is classified under manufacture of outerwear (NACE 14.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Skredder.”. The most recent filed accounts, for the 2025 financial year, show NOK 98,000 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 98,000
Operating profit
NOK −47,000
Equity
NOK −22,000

Financial health · 2025

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

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

Who owns LYKKE OG LITEN AS?

BERGIT LOUISE TVEIT
LYKKE OG LITEN AS
NOK 98,000 rev. · NOK −47,000 profit

LYKKE OG LITEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYKKE OG LITEN AS

Who owns LYKKE OG LITEN AS?

BERGIT LOUISE TVEIT is the largest registered owner, with 100.0%.

What is the revenue of LYKKE OG LITEN AS?

LYKKE OG LITEN AS had revenue of NOK 98,000 in 2025.

Who is the general manager of LYKKE OG LITEN AS?

Bergit Louise Tveit is registered as general manager of LYKKE OG LITEN AS.

Where is LYKKE OG LITEN AS based?

LYKKE OG LITEN AS has its business address in Haugesund.

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.