biztrac. BETA
COMPANY REGISTER PROFILE
835441652 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Retail sale of games and toys

LEKEKASSEN AS

Org. no. 835441652 Limited company (AS) Grimstad Incorporated 1984 Active
Ownership graph ↗
Revenue 2025 NOK 555.9m
Operating profit NOK 37.9m
Equity NOK 163.9m
Incorporated 1984
Employees 78
Share capital NOK 90,000

LEKEKASSEN AS is registered as a limited company in Grimstad, Agder with organisation number 835441652. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 1984 and has 78 registered employees. Registered share capital is NOK 90,000, divided into 180 shares. The company's stated purpose is: “Handel og annen økonomisk virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 555.9m in revenue and NOK 37.9m in operating profit.

Former names: LEIF SKALLEBERG AS

Key figures · 2025

Revenue
NOK 555.9m
▲ +11 %
Operating profit
NOK 37.9m
▼ −28 %
Equity
NOK 163.9m
▲ +71 %
Est. value
NOK 256.4m

Financial health · 2025

Liquidity
3.41
Very good
Current assets ÷ current liabilities
Profitability
17.6%
Very good
Return on total assets
Solidity
70.8%
Very good
Equity as a share of total capital

Who owns LEKEKASSEN AS?

LEKEKASSEN AS
NOK 555.9m rev. · NOK 37.9m profit

LEKEKASSEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LEKEKASSEN AS er morselskap for 4 datterselskaper:

Frequently asked questions about LEKEKASSEN AS

Who owns LEKEKASSEN AS?

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

What is the revenue of LEKEKASSEN AS?

LEKEKASSEN AS had revenue of NOK 555.9m in 2025.

Who is the general manager of LEKEKASSEN AS?

Kenneth Huse Halvorsen is registered as general manager of LEKEKASSEN AS.

Where is LEKEKASSEN AS based?

LEKEKASSEN AS has its business address in Grimstad.

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

Report a problem

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