BIZTRAC BETA
Publishing of video games

ARCTIC HAZARD HOLDING AS

Org. no. 929589181 Limited company (AS) Vestby Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK −20,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−20k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ARCTIC HAZARD HOLDING AS is registered as a limited company in Vestby, Akershus with organisation number 929589181. The business is classified under publishing of video games (NACE 58.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 99 shares. The company's stated purpose is: “Investering i aksjer, andre virksomheter og fast eiendom samt alt som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK −20,000

Financial health · 2025

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

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

Who owns ARCTIC HAZARD HOLDING AS?

Nils Terje Lundberg
ARCTIC HAZARD HOLDING AS
· NOK −11,000 profit

ARCTIC HAZARD HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ARCTIC HAZARD HOLDING AS own?

ARCTIC HAZARD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARCTIC HAZARD HOLDING AS

Who owns ARCTIC HAZARD HOLDING AS?

Nils Terje Lundberg is the largest registered owner, with 32.3%.

Where is ARCTIC HAZARD HOLDING AS based?

ARCTIC HAZARD HOLDING AS has its business address in Vestby.

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.