BIZTRAC BETA
Motion picture and video distribution activities

FILM 360 HOLDING AS

Org. no. 927479052 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −386,000
Equity NOK 3.7m
Incorporated 2021
Share capital NOK 144,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−386k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FILM 360 HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 927479052. The business is classified under motion picture and video distribution activities (NACE 59.130). The company was incorporated in 2021. Registered share capital is NOK 144,000, divided into 143858 shares. The company's stated purpose is: “Investeringer og alt som står i forbindelse med dette, herunder å eie aksjer og andeler i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −386,000
Equity
NOK 3.7m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns FILM 360 HOLDING AS?

SHOLDING AS
FILM 360 HOLDING AS
· NOK −386,000 profit

FILM 360 HOLDING AS has 13 registered shareholders:

All shareholders and roles →

Which companies does FILM 360 HOLDING AS own?

FILM 360 HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about FILM 360 HOLDING AS

Who owns FILM 360 HOLDING AS?

SHOLDING AS is the largest registered owner, with 48.3%.

Who is the general manager of FILM 360 HOLDING AS?

Svanhild Sørensen is registered as general manager of FILM 360 HOLDING AS.

Where is FILM 360 HOLDING AS based?

FILM 360 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.