BIZTRAC BETA
Activities of adventure companies

NORDLYSSENTERET AS

Org. no. 915677932 Limited company (AS) Tromsø Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 90,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

NORDLYSSENTERET AS is registered as a limited company in Tromsø, Troms with organisation number 915677932. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Etablere og drive et nordlyssenter i Tromsø.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 90,000
Est. value
NOK 112,000

Financial health · 2024

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

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

Who owns NORDLYSSENTERET AS?

ODD TORSTEN KRØNER ASLAKSEN
NORDLYSSENTERET AS
NOK 0 rev. · NOK −13,000 profit

NORDLYSSENTERET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORDLYSSENTERET AS

Who owns NORDLYSSENTERET AS?

ODD TORSTEN KRØNER ASLAKSEN is the largest registered owner, with 83.3%.

What is the revenue of NORDLYSSENTERET AS?

NORDLYSSENTERET AS had revenue of NOK 0 in 2024.

Who is the general manager of NORDLYSSENTERET AS?

Odd Torsten Krøner Aslaksen is registered as general manager of NORDLYSSENTERET AS.

Where is NORDLYSSENTERET AS based?

NORDLYSSENTERET 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.