biztrac. BETA
COMPANY REGISTER PROFILE
920254128 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Photographic activities

LYCKLIGA AS

Org. no. 920254128 Limited company (AS) Ullensaker Incorporated 2018 Active
Revenue 2025 NOK 1.8m
Operating profit NOK −65,000
Equity NOK −1.3m
Incorporated 2018
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).

LYCKLIGA AS is registered as a limited company in Ullensaker, Akershus with organisation number 920254128. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2018. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Fotografi, journalist og kursveileder og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −65,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +16 %
Operating profit
NOK −65,000
▼ −126 %
Equity
NOK −1.3m
▼ −624 %

Financial health · 2025

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
-3.5%
Not satisfactory
Return on total assets
Solidity
-199.7%
Weak
Equity as a share of total capital

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

Who owns LYCKLIGA AS?

LYCKLIGA AS
NOK 1.8m rev. · NOK −65,000 profit

LYCKLIGA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LYCKLIGA AS

Who owns LYCKLIGA AS?

May Hege Paulsen is the largest registered owner, with 100.0%.

What is the revenue of LYCKLIGA AS?

LYCKLIGA AS had revenue of NOK 1.8m in 2025.

Who is the general manager of LYCKLIGA AS?

May Hege Paulsen is registered as general manager of LYCKLIGA AS.

Where is LYCKLIGA AS based?

LYCKLIGA AS has its business address in Kløfta.

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.