BIZTRAC BETA
Radio broadcasting and audio distribution activities

APPLETIFY AS

Org. no. 916283776 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 10,000
Equity NOK 461,000
Incorporated 2015
Share capital NOK 32,000

APPLETIFY AS is registered as a limited company in Bærum, Akershus with organisation number 916283776. The business is classified under radio broadcasting and audio distribution activities (NACE 60.100). The company was incorporated in 2015. Registered share capital is NOK 32,000, divided into 31579 shares. The company's stated purpose is: “Markedsføring og salg av innholdstjenester innen musikk til profesjonelle brukere, samt tjenester og produkter som naturlig hører inn under dette, herunder også være forhandler av øvrige produkter og tjenester som er av interesse for denne kundegruppen.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 10,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 10,000
Equity
NOK 461,000
Est. value
NOK 3.7m

Financial health · 2024

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.0%
Satisfactory
Equity as a share of total capital

Who owns APPLETIFY AS?

HENNING DYNGVOLD SØRENSEN
APPLETIFY AS
NOK 4.3m rev. · NOK 10,000 profit

APPLETIFY AS has 3 registered shareholders:

All shareholders and roles →

Which companies does APPLETIFY AS own?

APPLETIFY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about APPLETIFY AS

Who owns APPLETIFY AS?

HENNING DYNGVOLD SØRENSEN is the largest registered owner, with 47.5%.

What is the revenue of APPLETIFY AS?

APPLETIFY AS had revenue of NOK 4.3m in 2024.

Where is APPLETIFY AS based?

APPLETIFY AS has its business address in Snarøya.

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.