BIZTRAC BETA
Computer consultancy and computer facilities management activities

BELINOX HOLDING AS

Org. no. 927453754 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 966,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

BELINOX HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 927453754. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 6000 shares. The company's stated purpose is: “Oppkjøp av, og investering i selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 966,000
Est. value
NOK 9.6m

Financial health · 2025

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

Who owns BELINOX HOLDING AS?

BERNARDO LINO DE OLIVEIRA
BELINOX HOLDING AS
NOK 0 rev. · NOK −12,000 profit

BELINOX HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BELINOX HOLDING AS

Who owns BELINOX HOLDING AS?

BERNARDO LINO DE OLIVEIRA is the largest registered owner, with 100.0%.

What is the revenue of BELINOX HOLDING AS?

BELINOX HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of BELINOX HOLDING AS?

Bernardo Lino De Oliveira is registered as general manager of BELINOX HOLDING AS.

Where is BELINOX HOLDING AS based?

BELINOX HOLDING AS has its business address in Kjeller.

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.