biztrac. BETA
COMPANY REGISTER PROFILE
916704313 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other non-specialised retail sale

BELIVA AS

Org. no. 916704313 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −488
Equity NOK 12
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−488 kr).
  • Nylig endring 2026-08-31 Adresseendring registrert 2026-08-31.

BELIVA AS is registered as a limited company in Oslo, Oslo with organisation number 916704313. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Handel, herunder netthandel, import, eksport, utvikling og salg av produkter og tjenester, utvikling og drift av merkevarer og nettbutikker, transportvirksomhet, samt kjøp, salg, eie, utvikling og utleie av fast eiendom og annen virksomhet som naturlig står i forbindelse med dette.”.

Former names: OLIVIER AS, LNM HOLDING AS, HANSEN BOLIGINVEST AS

Key figures · 2025

Operating profit
NOK −488
▼ −857 %
Equity
NOK 12
Est. value
NOK 15

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-8133.3%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns BELIVA AS?

BELIVA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BELIVA AS

Who owns BELIVA AS?

Lasse Hansen is the largest registered owner, with 50.0%.

Who is the general manager of BELIVA AS?

Mohammed Kamran Ashraf is registered as general manager of BELIVA AS.

Where is BELIVA AS based?

BELIVA 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.