BIZTRAC BETA
Retail sale of games and toys

LEKESENTERET AS

Org. no. 925178551 Limited company (AS) Nord-Aurdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 17,000
Equity NOK 1.5m
Incorporated 2020
Employees 8
Share capital NOK 800,000

LEKESENTERET AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 925178551. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2020 and has 8 registered employees. Registered share capital is NOK 800,000, divided into 800 shares. The company's stated purpose is: “Detaljhandel med hobby og leketøy, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 17,000
Equity
NOK 1.5m
Est. value
NOK 805,000

Financial health · 2025

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

Who owns LEKESENTERET AS?

STEIN RØNJUS HÅLIEN
LEKESENTERET AS
NOK 4.6m rev. · NOK 17,000 profit

LEKESENTERET AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LEKESENTERET AS own?

LEKESENTERET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEKESENTERET AS

Who owns LEKESENTERET AS?

STEIN RØNJUS HÅLIEN is the largest registered owner, with 60.0%.

What is the revenue of LEKESENTERET AS?

LEKESENTERET AS had revenue of NOK 4.6m in 2025.

Who is the general manager of LEKESENTERET AS?

Tonje Hålien is registered as general manager of LEKESENTERET AS.

Where is LEKESENTERET AS based?

LEKESENTERET AS has its business address in Leira I Valdres.

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.