BIZTRAC BETA
Retail sale of footwear and leather goods

BEKKESTUA SKO AS

Org. no. 927889552 Limited company (AS) Bærum Incorporated 1978 Active
Ownership graph ↗
Revenue 2024 NOK 35.5m
Operating profit NOK 2.5m
Equity NOK 17.5m
Incorporated 1978
Employees 43
Share capital NOK 900,000

BEKKESTUA SKO AS is registered as a limited company in Bærum, Akershus with organisation number 927889552. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 1978 and has 43 registered employees. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Handel og deltagelse i annen næringsvirksomhet med økonomiske formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 35.5m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 35.5m
Operating profit
NOK 2.5m
Equity
NOK 17.5m
Est. value
NOK 18.3m

Financial health · 2024

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

Who owns BEKKESTUA SKO AS?

HELAR HOLDING AS
BEKKESTUA SKO AS
NOK 35.5m rev. · NOK 2.5m profit

BEKKESTUA SKO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEKKESTUA SKO AS own?

BEKKESTUA SKO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BEKKESTUA SKO AS

Who owns BEKKESTUA SKO AS?

HELAR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BEKKESTUA SKO AS?

BEKKESTUA SKO AS had revenue of NOK 35.5m in 2024.

Who is the general manager of BEKKESTUA SKO AS?

Lars Elger is registered as general manager of BEKKESTUA SKO AS.

Where is BEKKESTUA SKO AS based?

BEKKESTUA SKO AS has its business address in Jar.

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.