BIZTRAC BETA
Retail sale of clothing

LEFDAL MÅLØY AS

Org. no. 991397140 Limited company (AS) Kinn Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK 713,000
Equity NOK 8.3m
Incorporated 2007
Employees 7
Share capital NOK 100,000

LEFDAL MÅLØY AS is registered as a limited company in Kinn, Vestland with organisation number 991397140. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2007 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og agentur og dermed sammenhengende virksomhet - herunder oppkjøp av aksjer m.v. for å kunne gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 713,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK 713,000
Equity
NOK 8.3m
Est. value
NOK 6.8m

Financial health · 2025

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

Who owns LEFDAL MÅLØY AS?

PER ARNE LEFDAL
LEFDAL MÅLØY AS
NOK 6.8m rev. · NOK 713,000 profit

LEFDAL MÅLØY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEFDAL MÅLØY AS own?

LEFDAL MÅLØY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEFDAL MÅLØY AS

Who owns LEFDAL MÅLØY AS?

PER ARNE LEFDAL is the largest registered owner, with 100.0%.

What is the revenue of LEFDAL MÅLØY AS?

LEFDAL MÅLØY AS had revenue of NOK 6.8m in 2025.

Who is the general manager of LEFDAL MÅLØY AS?

Per Arne Lefdal is registered as general manager of LEFDAL MÅLØY AS.

Where is LEFDAL MÅLØY AS based?

LEFDAL MÅLØY AS has its business address in Måløy.

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.