BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

JULELAND AS

Org. no. 929120043 Limited company (AS) Bodø Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 184,000
Operating profit NOK −22,000
Equity NOK 16,000
Incorporated 2022
Share capital NOK 90,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).
  • Nylig endring 2026-03-02 Aksjekapital registrert 2026-03-02.

JULELAND AS is registered as a limited company in Bodø, Nordland with organisation number 929120043. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2022. Registered share capital is NOK 90,000, divided into 180 shares. The company's stated purpose is: “Import og salg av dekor og pyntegjenstander.”. The most recent filed accounts, for the 2024 financial year, show NOK 184,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 184,000
Operating profit
NOK −22,000
Equity
NOK 16,000
Est. value
NOK 68,000

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.4%
Weak
Equity as a share of total capital

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

Who owns JULELAND AS?

ROGER ARNE JENSEN
JULELAND AS
NOK 184,000 rev. · NOK −22,000 profit

JULELAND AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about JULELAND AS

Who owns JULELAND AS?

ROGER ARNE JENSEN is the largest registered owner, with 25.0%.

What is the revenue of JULELAND AS?

JULELAND AS had revenue of NOK 184,000 in 2024.

Who is the general manager of JULELAND AS?

Cecilie Jenssen is registered as general manager of JULELAND AS.

Where is JULELAND AS based?

JULELAND AS has its business address in Bodø.

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.