BIZTRAC BETA
Development of building projects

EVLO INVEST AS

Org. no. 916513410 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK 3.6m
Equity NOK 24.4m
Incorporated 2015
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EVLO INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 916513410. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK 3.6m
Equity
NOK 24.4m
Est. value
NOK 25.2m

Financial health · 2024

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

Who owns EVLO INVEST AS?

JENS OLVE BØVRE
EVLO INVEST AS
NOK 4.0m rev. · NOK 3.6m profit

EVLO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EVLO INVEST AS own?

EVLO INVEST AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about EVLO INVEST AS

Who owns EVLO INVEST AS?

JENS OLVE BØVRE is the largest registered owner, with 100.0%.

What is the revenue of EVLO INVEST AS?

EVLO INVEST AS had revenue of NOK 4.0m in 2024.

Where is EVLO INVEST AS based?

EVLO INVEST 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.