BIZTRAC BETA
Rental and operating of own or leased real estate

BEVO INVEST AS

Org. no. 979450648 Limited company (AS) Fredrikstad Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 307,000
Operating profit NOK −262,000
Equity NOK 7.2m
Incorporated 1997
Share capital NOK 100,000

Signals

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

BEVO INVEST AS is registered as a limited company in Fredrikstad, Østfold with organisation number 979450648. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av verdipapirer og fast eiendom, og deltagelse i annen virksomhet ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 307,000 in revenue and NOK −262,000 in operating profit.

Key figures · 2025

Revenue
NOK 307,000
Operating profit
NOK −262,000
Equity
NOK 7.2m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns BEVO INVEST AS?

TOR ERIK BEKKEVOLD
BEVO INVEST AS
NOK 307,000 rev. · NOK −262,000 profit

BEVO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEVO INVEST AS own?

BEVO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BEVO INVEST AS

Who owns BEVO INVEST AS?

TOR ERIK BEKKEVOLD is the largest registered owner, with 100.0%.

What is the revenue of BEVO INVEST AS?

BEVO INVEST AS had revenue of NOK 307,000 in 2025.

Where is BEVO INVEST AS based?

BEVO INVEST AS has its business address in Fredrikstad.

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.