BIZTRAC BETA
Wholesale of clothing and footwear

SONIC AGENCY AS

Org. no. 919415347 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 15.5m
Operating profit NOK 2.6m
Equity NOK 4.0m
Incorporated 2017
Share capital NOK 30,000

SONIC AGENCY AS is registered as a limited company in Bærum, Akershus with organisation number 919415347. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Agenturvirksomhet innen kjøp/salg av klær, investering/deltakelse i andre selskaper, kjøp og salg av aksjer og andre verdipapirer samt alt som naturlig faller herunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.5m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 15.5m
Operating profit
NOK 2.6m
Equity
NOK 4.0m
Est. value
NOK 9.9m

Financial health · 2024

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.1%
Good
Equity as a share of total capital

Who owns SONIC AGENCY AS?

OLE LOSNEDAL
SONIC AGENCY AS
NOK 15.5m rev. · NOK 2.6m profit

SONIC AGENCY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SONIC AGENCY AS own?

SONIC AGENCY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SONIC AGENCY AS

Who owns SONIC AGENCY AS?

OLE LOSNEDAL is the largest registered owner, with 100.0%.

What is the revenue of SONIC AGENCY AS?

SONIC AGENCY AS had revenue of NOK 15.5m in 2024.

Who is the general manager of SONIC AGENCY AS?

Ole Losnedal is registered as general manager of SONIC AGENCY AS.

Where is SONIC AGENCY AS based?

SONIC AGENCY AS has its business address in Høvik.

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.