BIZTRAC BETA
Business and other management consultancy activities

BOBOLAI AS

Org. no. 999549640 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 620,000
Operating profit NOK −181,000
Equity NOK 249,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−181k kr).

BOBOLAI AS is registered as a limited company in Bærum, Akershus with organisation number 999549640. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen økonomi, administrasjon og ledelse, samt virksomhet som naturlig faller sammen med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 620,000 in revenue and NOK −181,000 in operating profit.

Key figures · 2024

Revenue
NOK 620,000
Operating profit
NOK −181,000
Equity
NOK 249,000
Est. value
NOK 772,000

Financial health · 2024

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

Who owns BOBOLAI AS?

ARNE KVAALEN FINSNES
BOBOLAI AS
NOK 620,000 rev. · NOK −181,000 profit

BOBOLAI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BOBOLAI AS own?

BOBOLAI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BOBOLAI AS

Who owns BOBOLAI AS?

ARNE KVAALEN FINSNES is the largest registered owner, with 100.0%.

What is the revenue of BOBOLAI AS?

BOBOLAI AS had revenue of NOK 620,000 in 2024.

Where is BOBOLAI AS based?

BOBOLAI AS has its business address in Bærums Verk.

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.