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

LILLEHAMMER INNREDNING AS

Org. no. 930744980 Limited company (AS) Lillehammer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 8.0m
Operating profit NOK −1.1m
Equity NOK −1.2m
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,2 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

LILLEHAMMER INNREDNING AS is registered as a limited company in Lillehammer, Innlandet with organisation number 930744980. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av innredning.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.0m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 8.0m
Operating profit
NOK −1.1m
Equity
NOK −1.2m

Financial health · 2024

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

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

Who owns LILLEHAMMER INNREDNING AS?

ES-HOLDING AS
LILLEHAMMER INNREDNING AS
NOK 8.0m rev. · NOK −1.1m profit

LILLEHAMMER INNREDNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER INNREDNING AS

Who owns LILLEHAMMER INNREDNING AS?

ES-HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LILLEHAMMER INNREDNING AS?

LILLEHAMMER INNREDNING AS had revenue of NOK 8.0m in 2024.

Where is LILLEHAMMER INNREDNING AS based?

LILLEHAMMER INNREDNING AS has its business address in Lillehammer.

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.