BIZTRAC BETA
Activities of excursion and event organisers

AMAZING AURORA AS

Org. no. 920577954 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 16.0m
Operating profit NOK 8.7m
Equity NOK 12.6m
Incorporated 2018
Employees 15
Share capital NOK 30,000

AMAZING AURORA AS is registered as a limited company in Tromsø, Troms with organisation number 920577954. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2018 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilrettelegging og formidling av ekskursjoner for turister. Tilveiebringelse og formidling av pakkereiser. Tilveiebringelse, formidling og tilrettelegging av overnatting til gjester.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.0m in revenue and NOK 8.7m in operating profit.

Key figures · 2024

Revenue
NOK 16.0m
Operating profit
NOK 8.7m
Equity
NOK 12.6m
Est. value
NOK 35.3m

Financial health · 2024

Liquidity
2.13
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
74.6%
Very good
Equity as a share of total capital

Who owns AMAZING AURORA AS?

MANSOOR WAIZY
AMAZING AURORA AS
NOK 16.0m rev. · NOK 8.7m profit

AMAZING AURORA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AMAZING AURORA AS

Who owns AMAZING AURORA AS?

MANSOOR WAIZY is the largest registered owner, with 100.0%.

What is the revenue of AMAZING AURORA AS?

AMAZING AURORA AS had revenue of NOK 16.0m in 2024.

Who is the general manager of AMAZING AURORA AS?

Mansoor Waizy is registered as general manager of AMAZING AURORA AS.

Where is AMAZING AURORA AS based?

AMAZING AURORA 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.