BIZTRAC BETA
Retail sale of textiles

ULDVAREN AS

Org. no. 881160692 Limited company (AS) Lillehammer Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 8.0m
Operating profit NOK −754,000
Equity NOK 382,000
Incorporated 1999
Employees 13
Share capital NOK 540,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−754k kr).

ULDVAREN AS is registered as a limited company in Lillehammer, Innlandet with organisation number 881160692. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 1999 and has 13 registered employees. Registered share capital is NOK 540,000, divided into 5000 shares. The company's stated purpose is: “Butikkhandel med tekstiler og utstyrsvarer.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.0m in revenue and NOK −754,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.0m
Operating profit
NOK −754,000
Equity
NOK 382,000
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.7%
Good
Equity as a share of total capital

Who owns ULDVAREN AS?

HUSFLIDEN LILLEHAMMER
ULDVAREN AS
NOK 8.0m rev. · NOK −754,000 profit

ULDVAREN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ULDVAREN AS own?

ULDVAREN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULDVAREN AS

Who owns ULDVAREN AS?

HUSFLIDEN LILLEHAMMER is the largest registered owner, with 100.0%.

What is the revenue of ULDVAREN AS?

ULDVAREN AS had revenue of NOK 8.0m in 2024.

Who is the general manager of ULDVAREN AS?

Evy Ruststuen Sunde is registered as general manager of ULDVAREN AS.

Where is ULDVAREN AS based?

ULDVAREN 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.