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

FRODE LEDAL AS

Org. no. 987276010 Limited company (AS) Oppdal Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 143.7m
Operating profit NOK 3.0m
Equity NOK 5.2m
Incorporated 2004
Employees 29
Share capital NOK 500,000

FRODE LEDAL AS is registered as a limited company in Oppdal, Trøndelag with organisation number 987276010. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2004 and has 29 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 143.7m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 143.7m
Operating profit
NOK 3.0m
Equity
NOK 5.2m
Est. value
NOK 14.2m

Financial health · 2025

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

Who owns FRODE LEDAL AS?

FRODE LEDAL
FRODE LEDAL AS
NOK 143.7m rev. · NOK 3.0m profit

FRODE LEDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRODE LEDAL AS

Who owns FRODE LEDAL AS?

FRODE LEDAL is the largest registered owner, with 100.0%.

What is the revenue of FRODE LEDAL AS?

FRODE LEDAL AS had revenue of NOK 143.7m in 2025.

Who is the general manager of FRODE LEDAL AS?

Frode Ledal is registered as general manager of FRODE LEDAL AS.

Where is FRODE LEDAL AS based?

FRODE LEDAL AS has its business address in Oppdal.

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.