BIZTRAC BETA
Computer programming activities

SYNCHRONICITY MEDIA AS

Org. no. 833459252 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −811,000
Equity NOK 2.4m
Incorporated 2024
Share capital NOK 34,000

Signals

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

SYNCHRONICITY MEDIA AS is registered as a limited company in Bergen, Vestland with organisation number 833459252. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 34,000, divided into 3411819 shares. The company's stated purpose is: “Holdingselskap med formål om å investere, og eie selskaper innenfor innovasjon, teknologi- og produktutvikling innenfor film, TV, musikk, broadcast og mediaproduksjon herunder digitale løsninger, investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet. Selskapet vil eie datterselskaper i Norge, USA og Canada.”.

Key figures · 2024

Operating profit
NOK −811,000
Equity
NOK 2.4m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns SYNCHRONICITY MEDIA AS?

LUCHS FAMILY TRUST
SYNCHRONICITY MEDIA AS
· NOK −811,000 profit

SYNCHRONICITY MEDIA AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SYNCHRONICITY MEDIA AS own?

SYNCHRONICITY MEDIA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SYNCHRONICITY MEDIA AS

Who owns SYNCHRONICITY MEDIA AS?

LUCHS FAMILY TRUST is the largest registered owner, with 14.3%.

Where is SYNCHRONICITY MEDIA AS based?

SYNCHRONICITY MEDIA AS has its business address in Nesttun.

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.