BIZTRAC BETA
COMPANY REGISTER PROFILE
948267497 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Retail sale of hardware, building materials, paints and glass

M LEIKNES AS

Org. no. 948267497 Limited company (AS) Askvoll Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 20.8m
Operating profit NOK −575,000
Equity NOK 5.4m
Incorporated 1988
Employees 7
Share capital NOK 139,000

Signals

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

M LEIKNES AS is registered as a limited company in Askvoll, Vestland with organisation number 948267497. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 1988 and has 7 registered employees. Registered share capital is NOK 139,000. The company's stated purpose is: “Produksjon og handel innan byggjevarer og trelast.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.8m in revenue and NOK −575,000 in operating profit.

Key figures · 2025

Revenue
NOK 20.8m
▲ +0 %
Operating profit
NOK −575,000
▼ −532 %
Equity
NOK 5.4m
▼ −9 %
Est. value
NOK 8.6m

Financial health · 2025

Liquidity
2.41
Very good
Current assets ÷ current liabilities
Profitability
-5.6%
Not satisfactory
Return on total assets
Solidity
56.9%
Very good
Equity as a share of total capital

Who owns M LEIKNES AS?

M LEIKNES AS has 3 registered shareholders:

All shareholders and roles →

Which companies does M LEIKNES AS own?

M LEIKNES AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about M LEIKNES AS

Who owns M LEIKNES AS?

ARVE MAGNAR LEIKNES is the largest registered owner, with 37.9%.

What is the revenue of M LEIKNES AS?

M LEIKNES AS had revenue of NOK 20.8m in 2025.

Where is M LEIKNES AS based?

M LEIKNES AS has its business address in Askvoll.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.