BIZTRAC BETA
COMPANY REGISTER PROFILE
932740575 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

BELAY AI AS

Org. no. 932740575 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 500,000
Operating profit NOK −8,000
Equity NOK 22,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

BELAY AI AS is registered as a limited company in Oslo, Oslo with organisation number 932740575. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og kommersialisering av programvare.”. The most recent filed accounts, for the 2024 financial year, show NOK 500,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 500,000
Operating profit
NOK −8,000
Equity
NOK 22,000
Est. value
NOK 854,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BELAY AI AS?

JORGE EDUARDO HERMOSO VALLE
BELAY AI AS
NOK 500,000 rev. · NOK −8,000 profit

BELAY AI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BELAY AI AS

Who owns BELAY AI AS?

JORGE EDUARDO HERMOSO VALLE is the largest registered owner, with 100.0%.

What is the revenue of BELAY AI AS?

BELAY AI AS had revenue of NOK 500,000 in 2024.

Who is the general manager of BELAY AI AS?

Jorge Eduardo Hermoso Valle is registered as general manager of BELAY AI AS.

Where is BELAY AI AS based?

BELAY AI 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.