biztrac. BETA
COMPANY REGISTER PROFILE
930341657 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

CLOUDBERRIES ECHO AS

Org. no. 930341657 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 25.4m
Operating profit NOK 2.4m
Equity NOK 2.9m
Incorporated 2022
Employees 13
Share capital NOK 30,000

CLOUDBERRIES ECHO AS is registered as a limited company in Oslo, Oslo with organisation number 930341657. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 3000000 shares. The company's stated purpose is: “Salg og leveranse av tjenester, løsninger og annet innen innovasjons- og digitaliseringsindustrien. Samt annen virksomhet som naturlig faller innenfor dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.4m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 25.4m
▲ +27 %
Operating profit
NOK 2.4m
▲ +10 %
Equity
NOK 2.9m
▲ +8 %
Est. value
NOK 14.9m

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
24.1%
Very good
Return on total assets
Solidity
27.9%
Good
Equity as a share of total capital

Who owns CLOUDBERRIES ECHO AS?

CLOUDBERRIES ECHO AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLOUDBERRIES ECHO AS

Who owns CLOUDBERRIES ECHO AS?

CLOUDBERRIES AS is the largest registered owner, with 79.0%.

What is the revenue of CLOUDBERRIES ECHO AS?

CLOUDBERRIES ECHO AS had revenue of NOK 25.4m in 2025.

Where is CLOUDBERRIES ECHO AS based?

CLOUDBERRIES ECHO 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.