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

ÅDNE DIRDAL AS

Org. no. 986083855 Limited company (AS) Gjesdal Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 108.7m
Operating profit NOK 2.2m
Equity NOK 1.8m
Incorporated 2003
Employees 20
Share capital NOK 500,000

ÅDNE DIRDAL AS is registered as a limited company in Gjesdal, Rogaland with organisation number 986083855. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2003 and has 20 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Er 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 108.7m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 108.7m
Operating profit
NOK 2.2m
Equity
NOK 1.8m
Est. value
NOK 9.7m

Financial health · 2025

Liquidity
1.03
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 ÅDNE DIRDAL AS?

ÅDNE DIRDAL
ÅDNE DIRDAL AS
NOK 108.7m rev. · NOK 2.2m profit

ÅDNE DIRDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅDNE DIRDAL AS

Who owns ÅDNE DIRDAL AS?

ÅDNE DIRDAL is the largest registered owner, with 100.0%.

What is the revenue of ÅDNE DIRDAL AS?

ÅDNE DIRDAL AS had revenue of NOK 108.7m in 2025.

Who is the general manager of ÅDNE DIRDAL AS?

Ådne Dirdal is registered as general manager of ÅDNE DIRDAL AS.

Where is ÅDNE DIRDAL AS based?

ÅDNE DIRDAL AS has its business address in Ålgård.

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.