biztrac. BETA
COMPANY REGISTER PROFILE
935240972 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of clothing

LUCKYBAG AS

Org. no. 935240972 Limited company (AS) Rælingen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 79,000
Operating profit NOK −96,000
Equity NOK −36,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

LUCKYBAG AS is registered as a limited company in Rælingen, Akershus with organisation number 935240972. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen klær, sko og utstyr via netthandel og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 79,000 in revenue and NOK −96,000 in operating profit.

Key figures · 2025

Revenue
NOK 79,000
Operating profit
NOK −96,000
Equity
NOK −36,000

Financial health · 2025

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

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

Who owns LUCKYBAG AS?

LUCKYBAG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUCKYBAG AS

Who owns LUCKYBAG AS?

THUNDERSTORM INVEST AS is the largest registered owner, with 38.9%.

What is the revenue of LUCKYBAG AS?

LUCKYBAG AS had revenue of NOK 79,000 in 2025.

Where is LUCKYBAG AS based?

LUCKYBAG AS has its business address in Fjerdingby.

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.