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

LEO'S AS

Org. no. 930848050 Limited company (AS) Trondheim Incorporated 2023 Active
Revenue 2025 NOK 6.0m
Operating profit NOK 158,000
Equity NOK −1.6m
Incorporated 2023
Employees 19
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).

LEO'S AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930848050. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 19 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Restaurant og take away, og andre tilhørende aktiviteter. Salg og produksjon av matprodukter og drikke.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 158,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
▲ +19 %
Operating profit
NOK 158,000
▲ +122 %
Equity
NOK −1.6m
▲ +9 %

Financial health · 2025

Liquidity
0.27
Not satisfactory
Current assets ÷ current liabilities
Profitability
9.9%
Satisfactory
Return on total assets
Solidity
-100.4%
Weak
Equity as a share of total capital

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

Who owns LEO'S AS?

LEO'S AS
NOK 6.0m rev. · NOK 158,000 profit

LEO'S AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEO'S AS

Who owns LEO'S AS?

Nicolo Rossi is the largest registered owner, with 100.0%.

What is the revenue of LEO'S AS?

LEO'S AS had revenue of NOK 6.0m in 2025.

Who is the general manager of LEO'S AS?

Nicolo Rossi is registered as general manager of LEO'S AS.

Where is LEO'S AS based?

LEO'S AS has its business address in Trondheim.

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.