BIZTRAC BETA
Industrial product and fashion design activities

LUCKYBILLY AS

Org. no. 922264872 Limited company (AS) Ringerike Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 249
Operating profit NOK −63,000
Equity NOK −35,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

LUCKYBILLY AS is registered as a limited company in Ringerike, Buskerud with organisation number 922264872. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Rideklær og hesteutstyr”. The most recent filed accounts, for the 2025 financial year, show NOK 249 in revenue and NOK −63,000 in operating profit.

Key figures · 2025

Revenue
NOK 249
Operating profit
NOK −63,000
Equity
NOK −35,000

Financial health · 2025

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

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

Who owns LUCKYBILLY AS?

NORA KLEVEN HALSE
LUCKYBILLY AS
NOK 249 rev. · NOK −63,000 profit

LUCKYBILLY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUCKYBILLY AS

Who owns LUCKYBILLY AS?

NORA KLEVEN HALSE is the largest registered owner, with 50.0%.

What is the revenue of LUCKYBILLY AS?

LUCKYBILLY AS had revenue of NOK 249 in 2025.

Who is the general manager of LUCKYBILLY AS?

Helene Preus is registered as general manager of LUCKYBILLY AS.

Where is LUCKYBILLY AS based?

LUCKYBILLY AS has its business address in Hønefoss.

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.