BIZTRAC BETA
Retail sale of games and toys

SESAM LEKER AS

Org. no. 976899555 Limited company (AS) Nordreisa Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 494,000
Equity NOK 335,000
Incorporated 1996
Employees 8
Share capital NOK 100,000

SESAM LEKER AS is registered as a limited company in Nordreisa, Troms with organisation number 976899555. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 1996 and has 8 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Butikkhandel med leker. Kioskhandel. Selskapet skal også kunne delta i andre selskaper med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 494,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
Operating profit
NOK 494,000
Equity
NOK 335,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.8%
Good
Equity as a share of total capital

Who owns SESAM LEKER AS?

SESAM LEKER HOLDING AS
SESAM LEKER AS
NOK 6.6m rev. · NOK 494,000 profit

SESAM LEKER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SESAM LEKER AS own?

SESAM LEKER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SESAM LEKER AS

Who owns SESAM LEKER AS?

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

What is the revenue of SESAM LEKER AS?

SESAM LEKER AS had revenue of NOK 6.6m in 2025.

Who is the general manager of SESAM LEKER AS?

Kaja Helene Olsen Mikkelsen is registered as general manager of SESAM LEKER AS.

Where is SESAM LEKER AS based?

SESAM LEKER AS has its business address in Storslett.

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.