biztrac. BETA
COMPANY REGISTER PROFILE
927028034 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

OLVE INVEST AS

Org. no. 927028034 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 15,000
Operating profit NOK −2,000
Equity NOK 11.8m
Incorporated 2021
Share capital NOK 4.4m

Signals

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

OLVE INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 927028034. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 4.4m, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper og aksjer, samt investering i ulike typer eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
Operating profit
NOK −2,000
▲ +89 %
Equity
NOK 11.8m
▲ +7 %
Est. value
NOK 9.8m

Financial health · 2025

Liquidity
15.16
Very good
Current assets ÷ current liabilities
Profitability
8.0%
Satisfactory
Return on total assets
Solidity
93.6%
Very good
Equity as a share of total capital

Who owns OLVE INVEST AS?

OLVE INVEST AS
NOK 15,000 rev. · NOK −2,000 profit

OLVE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLVE INVEST AS own?

OLVE INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLVE INVEST AS

Who owns OLVE INVEST AS?

Ole-Johan Vernøy is the largest registered owner, with 100.0%.

What is the revenue of OLVE INVEST AS?

OLVE INVEST AS had revenue of NOK 15,000 in 2025.

Where is OLVE INVEST AS based?

OLVE INVEST AS has its business address in Sandsli.

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.