BIZTRAC BETA
Manufacture of fruit and vegetable juice

EPLI SIDERI AS

Org. no. 815099982 Limited company (AS) Ullensvang Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK −346,000
Equity NOK 952,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−346k kr).

EPLI SIDERI AS is registered as a limited company in Ullensvang, Vestland with organisation number 815099982. The business is classified under manufacture of fruit and vegetable juice (NACE 10.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon, distribusjon og salg av eplesider og annen tilsvarende virksomhet, samt eierskap i andre selskaper og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK −346,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK −346,000
Equity
NOK 952,000
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
2.61
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.1%
Good
Equity as a share of total capital

Who owns EPLI SIDERI AS?

LELI HOLDING AS
EPLI SIDERI AS
NOK 6.2m rev. · NOK −346,000 profit

EPLI SIDERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EPLI SIDERI AS

Who owns EPLI SIDERI AS?

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

What is the revenue of EPLI SIDERI AS?

EPLI SIDERI AS had revenue of NOK 6.2m in 2025.

Who is the general manager of EPLI SIDERI AS?

Kristian Sekse Andersen is registered as general manager of EPLI SIDERI AS.

Where is EPLI SIDERI AS based?

EPLI SIDERI AS has its business address in Hovland.

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.