BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ULEFOSS DAGLIGVARE AS

Org. no. 915808492 Limited company (AS) Nome Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 86.3m
Operating profit NOK 3.7m
Equity NOK 4.4m
Incorporated 2015
Employees 22
Share capital NOK 700,000

ULEFOSS DAGLIGVARE AS is registered as a limited company in Nome, Telemark with organisation number 915808492. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2015 and has 22 registered employees. Registered share capital is NOK 700,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med dagligvarer, samt annen virksomhet som står i nær sammenheng til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 86.3m in revenue and NOK 3.7m in operating profit.

Key figures · 2024

Revenue
NOK 86.3m
Operating profit
NOK 3.7m
Equity
NOK 4.4m
Est. value
NOK 16.8m

Financial health · 2024

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

Who owns ULEFOSS DAGLIGVARE AS?

LØKKABAKKEN HOLDING AS
ULEFOSS DAGLIGVARE AS
NOK 86.3m rev. · NOK 3.7m profit

ULEFOSS DAGLIGVARE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ULEFOSS DAGLIGVARE AS

Who owns ULEFOSS DAGLIGVARE AS?

LØKKABAKKEN HOLDING AS is the largest registered owner, with 66.0%.

What is the revenue of ULEFOSS DAGLIGVARE AS?

ULEFOSS DAGLIGVARE AS had revenue of NOK 86.3m in 2024.

Who is the general manager of ULEFOSS DAGLIGVARE AS?

Thor Arnesen is registered as general manager of ULEFOSS DAGLIGVARE AS.

Where is ULEFOSS DAGLIGVARE AS based?

ULEFOSS DAGLIGVARE AS has its business address in Ulefoss.

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.