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

AMORE ORKANGER AS

Org. no. 921480903 Limited company (AS) Orkland Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 250,000
Equity NOK 505,000
Incorporated 2018
Employees 7
Share capital NOK 30,000

AMORE ORKANGER AS is registered as a limited company in Orkland, Trøndelag with organisation number 921480903. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift av restaurant, bar og deltakelse i andre lignende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 250,000 in operating profit.

Former names: KONSTADHAVEN PIZZERIA AS

Key figures · 2025

Revenue
NOK 6.0m
▲ +30 %
Operating profit
NOK 250,000
▲ +912 %
Equity
NOK 505,000
▲ +62 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
21.9%
Very good
Return on total assets
Solidity
39.7%
Good
Equity as a share of total capital

Who owns AMORE ORKANGER AS?

AMORE ORKANGER AS
NOK 6.0m rev. · NOK 250,000 profit

AMORE ORKANGER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AMORE ORKANGER AS

Who owns AMORE ORKANGER AS?

Gyulnaz Tefik Ilyaz is the largest registered owner, with 50.0%.

What is the revenue of AMORE ORKANGER AS?

AMORE ORKANGER AS had revenue of NOK 6.0m in 2025.

Who is the general manager of AMORE ORKANGER AS?

Gyulnaz Tefik Ilyaz is registered as general manager of AMORE ORKANGER AS.

Where is AMORE ORKANGER AS based?

AMORE ORKANGER AS has its business address in Orkanger.

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.