BIZTRAC BETA
COMPANY REGISTER PROFILE
815385012 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other real estate activities on a fee or contract basis

BELLIS ECOINVEST AS

Org. no. 815385012 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK −116,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−116k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

BELLIS ECOINVEST AS is registered as a limited company in Oslo, Oslo with organisation number 815385012. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Forvaltning av egen formue, erverv og forvaltning samt utleie av egen fast eiendom og erverv av andeler i andre foretak. Generelt skal selskapet kunne foreta industrielle, kommersielle og finansielle handlinger og i tillegg inngå avtaler om fast eiendom i tilknytning til selskapets virksomhet.”.

Key figures · 2025

Operating profit
NOK −9,000
Equity
NOK −116,000

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.7%
Weak
Equity as a share of total capital

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

Who owns BELLIS ECOINVEST AS?

SVEN HERRMANN
BELLIS ECOINVEST AS
· NOK −9,000 profit

BELLIS ECOINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BELLIS ECOINVEST AS

Who owns BELLIS ECOINVEST AS?

SVEN HERRMANN is the largest registered owner, with 100.0%.

Where is BELLIS ECOINVEST AS based?

BELLIS ECOINVEST 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.