BIZTRAC BETA
COMPANY REGISTER PROFILE
827082872 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

ARTI HOLDING AS

Org. no. 827082872 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11
Equity NOK 24,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

ARTI HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 827082872. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer, samt andre investeringer og oppgaver som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11
Equity
NOK 24,000
Est. value
NOK 29,000

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.3%
Weak
Equity as a share of total capital

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

Who owns ARTI HOLDING AS?

ARTURAS VAITKEVICIUS
ARTI HOLDING AS
NOK 0 rev. · NOK −11 profit

ARTI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARTI HOLDING AS

Who owns ARTI HOLDING AS?

ARTURAS VAITKEVICIUS is the largest registered owner, with 100.0%.

What is the revenue of ARTI HOLDING AS?

ARTI HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of ARTI HOLDING AS?

Arturas Vaitkevicius is registered as general manager of ARTI HOLDING AS.

Where is ARTI HOLDING AS based?

ARTI HOLDING AS has its business address in Oslo.

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.