BIZTRAC BETA
Rental and operating of own or leased real estate

BØ INVEST AS

Org. no. 979709706 Limited company (AS) Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK −12,000
Equity NOK 3.6m
Incorporated 1998
Share capital NOK 600,000

Signals

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

BØ INVEST AS is registered as a limited company in Bø, Nordland with organisation number 979709706. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Investeringer i objekter som kan leies ut, samt være med som medeier i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK −12,000
Equity
NOK 3.6m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
1.88
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.9%
Good
Equity as a share of total capital

Who owns BØ INVEST AS?

JAN ARILD ANDERSEN
BØ INVEST AS
NOK 1.9m rev. · NOK −12,000 profit

BØ INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BØ INVEST AS own?

BØ INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BØ INVEST AS

Who owns BØ INVEST AS?

JAN ARILD ANDERSEN is the largest registered owner, with 60.0%.

What is the revenue of BØ INVEST AS?

BØ INVEST AS had revenue of NOK 1.9m in 2025.

Who is the general manager of BØ INVEST AS?

Jan Arild Andersen is registered as general manager of BØ INVEST AS.

Where is BØ INVEST AS based?

BØ INVEST AS has its business address in Bø I Vesterålen.

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.