BIZTRAC BETA
Rental and operating of own or leased real estate

LØKKY AS

Org. no. 931310747 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 254,000
Operating profit NOK 128,000
Equity NOK −178,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−178k kr).

LØKKY AS is registered as a limited company in Oslo, Oslo with organisation number 931310747. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av fast eiendom - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 254,000 in revenue and NOK 128,000 in operating profit.

Key figures · 2024

Revenue
NOK 254,000
Operating profit
NOK 128,000
Equity
NOK −178,000
Est. value
NOK 878,000

Financial health · 2024

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

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

Who owns LØKKY AS?

KEVIN VAN DOAN
LØKKY AS
NOK 254,000 rev. · NOK 128,000 profit

LØKKY AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØKKY AS

Who owns LØKKY AS?

KEVIN VAN DOAN is the largest registered owner, with 29.5%.

What is the revenue of LØKKY AS?

LØKKY AS had revenue of NOK 254,000 in 2024.

Who is the general manager of LØKKY AS?

Elton Wong is registered as general manager of LØKKY AS.

Where is LØKKY AS based?

LØKKY 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.