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

LI2 DIGERNES AS

Org. no. 929524519 Limited company (AS) Ålesund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 96.3m
Operating profit NOK 2.0m
Equity NOK 1.8m
Incorporated 2022
Employees 23
Share capital NOK 500,000

LI2 DIGERNES AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 929524519. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2022 and has 23 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 96.3m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 96.3m
Operating profit
NOK 2.0m
Equity
NOK 1.8m
Est. value
NOK 8.9m

Financial health · 2025

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

Who owns LI2 DIGERNES AS?

LI2 INVEST AS
LI2 DIGERNES AS
NOK 96.3m rev. · NOK 2.0m profit

LI2 DIGERNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LI2 DIGERNES AS

Who owns LI2 DIGERNES AS?

LI2 INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LI2 DIGERNES AS?

LI2 DIGERNES AS had revenue of NOK 96.3m in 2025.

Who is the general manager of LI2 DIGERNES AS?

Liv Tuva is registered as general manager of LI2 DIGERNES AS.

Where is LI2 DIGERNES AS based?

LI2 DIGERNES AS has its business address in Skodje.

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.