BIZTRAC BETA
Business and other management consultancy activities

RESONATE X CHANGE AS

Org. no. 923484906 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 38,000
Operating profit NOK 11,000
Equity NOK 274,000
Incorporated 2019
Share capital NOK 30,000

RESONATE X CHANGE AS is registered as a limited company in Oslo, Oslo with organisation number 923484906. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bedriftsrådgiving”. The most recent filed accounts, for the 2025 financial year, show NOK 38,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 38,000
Operating profit
NOK 11,000
Equity
NOK 274,000
Est. value
NOK 173,000

Financial health · 2025

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

Who owns RESONATE X CHANGE AS?

INGVILD SØRFLATEN MOEN
RESONATE X CHANGE AS
NOK 38,000 rev. · NOK 11,000 profit

RESONATE X CHANGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RESONATE X CHANGE AS own?

RESONATE X CHANGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RESONATE X CHANGE AS

Who owns RESONATE X CHANGE AS?

INGVILD SØRFLATEN MOEN is the largest registered owner, with 100.0%.

What is the revenue of RESONATE X CHANGE AS?

RESONATE X CHANGE AS had revenue of NOK 38,000 in 2025.

Who is the general manager of RESONATE X CHANGE AS?

Ingvild Sørflaten Moen is registered as general manager of RESONATE X CHANGE AS.

Where is RESONATE X CHANGE AS based?

RESONATE X CHANGE 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.