biztrac. BETA
COMPANY REGISTER PROFILE
936704719 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

YY LECK TROMSØ AS

Org. no. 936704719 Limited company (AS) Tromsø Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 26,000
Incorporated 2025
Employees 9
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

YY LECK TROMSØ AS is registered as a limited company in Tromsø, Troms with organisation number 936704719. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive en restaurant eller kafé, inkludert, men ikke begrenset til, salg av mat- og drikkevarer for konsum på stedet, take-away og eventuell levering.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 26,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns YY LECK TROMSØ AS?

YY LECK TROMSØ AS
NOK 0 rev. · NOK −4,000 profit

YY LECK TROMSØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YY LECK TROMSØ AS

Who owns YY LECK TROMSØ AS?

Suksawat Suksomboon is the largest registered owner, with 100.0%.

What is the revenue of YY LECK TROMSØ AS?

YY LECK TROMSØ AS had revenue of NOK 0 in 2025.

Where is YY LECK TROMSØ AS based?

YY LECK TROMSØ AS has its business address in Tromsø.

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.