BIZTRAC BETA
Computer programming activities

SKYFALL 22 AS

Org. no. 920897444 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK 1.5m
Incorporated 2018
Share capital NOK 1.6m

Signals

2 flags
  • Driftsunderskudd 2024 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.

SKYFALL 22 AS is registered as a limited company in Oslo, Oslo with organisation number 920897444. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2018. Registered share capital is NOK 1.6m, divided into 1597756 shares. The company's stated purpose is: “Investering i tidligfase-selskaper, salg av konsulenttjenester samt relatert virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 1.5m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns SKYFALL 22 AS?

SKYFALL INVEST AS
SKYFALL 22 AS
NOK 0 rev. · NOK −11,000 profit

SKYFALL 22 AS has 9 registered shareholders:

All shareholders and roles →

Which companies does SKYFALL 22 AS own?

SKYFALL 22 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SKYFALL 22 AS

Who owns SKYFALL 22 AS?

SKYFALL INVEST AS is the largest registered owner, with 58.4%.

What is the revenue of SKYFALL 22 AS?

SKYFALL 22 AS had revenue of NOK 0 in 2024.

Where is SKYFALL 22 AS based?

SKYFALL 22 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.