BIZTRAC BETA
Rental and operating of own or leased real estate

ARCTIC TIGERS AS

Org. no. 929868226 Limited company (AS) Molde Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 253,000
Operating profit NOK −50,000
Equity NOK 811,000
Incorporated 2022
Share capital NOK 1.9m

Signals

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

ARCTIC TIGERS AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 929868226. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 1.9m, divided into 1900000 shares. The company's stated purpose is: “Selskapets formål er å drive med utleie av bolig og verktøy/redskap, utleie av personell og maskiner/kjøretøy og herunder gods- og person-transport. og andre tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 253,000 in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 253,000
Operating profit
NOK −50,000
Equity
NOK 811,000
Est. value
NOK 740,000

Financial health · 2024

Liquidity
-0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.0%
Good
Equity as a share of total capital

Who owns ARCTIC TIGERS AS?

JEYANTHARAJ VARATHARAJAH
ARCTIC TIGERS AS
NOK 253,000 rev. · NOK −50,000 profit

ARCTIC TIGERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARCTIC TIGERS AS

Who owns ARCTIC TIGERS AS?

JEYANTHARAJ VARATHARAJAH is the largest registered owner, with 100.0%.

What is the revenue of ARCTIC TIGERS AS?

ARCTIC TIGERS AS had revenue of NOK 253,000 in 2024.

Where is ARCTIC TIGERS AS based?

ARCTIC TIGERS AS has its business address in Molde.

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.