BIZTRAC BETA
Retail sale of games and toys

YES VI LEKER TVEITA AS

Org. no. 916944608 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −166,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−166k kr).

YES VI LEKER TVEITA AS is registered as a limited company in Oslo, Oslo with organisation number 916944608. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av spill og leker til barn, samt investering i andre selskaper og alt som dertil naturlig hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −166,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-956.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns YES VI LEKER TVEITA AS?

MARDAN SAEED
YES VI LEKER TVEITA AS
NOK 0 rev. · NOK 0 profit

YES VI LEKER TVEITA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YES VI LEKER TVEITA AS

Who owns YES VI LEKER TVEITA AS?

MARDAN SAEED is the largest registered owner, with 100.0%.

What is the revenue of YES VI LEKER TVEITA AS?

YES VI LEKER TVEITA AS had revenue of NOK 0 in 2025.

Who is the general manager of YES VI LEKER TVEITA AS?

Mardan Saeed is registered as general manager of YES VI LEKER TVEITA AS.

Where is YES VI LEKER TVEITA AS based?

YES VI LEKER TVEITA AS has its business address in Oslo.

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.