BIZTRAC BETA
Business and other management consultancy activities

ABO SERVICE AS

Org. no. 920916562 Limited company (AS) Bærum Incorporated 1981 Active
Ownership graph ↗
Revenue 2024 NOK 689,000
Operating profit NOK −34,000
Equity NOK 308,000
Incorporated 1981
Share capital NOK 200,000

Signals

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

ABO SERVICE AS is registered as a limited company in Bærum, Akershus with organisation number 920916562. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1981. Registered share capital is NOK 200,000, divided into 500 shares. The company's stated purpose is: “Konsulentvirksomhet og utleie av driftsmidler og arbeidskraft. Det skal være anledning til å investere i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 689,000 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 689,000
Operating profit
NOK −34,000
Equity
NOK 308,000
Est. value
NOK 726,000

Financial health · 2024

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

Who owns ABO SERVICE AS?

ESPEN ROAR BAKKE
ABO SERVICE AS
NOK 689,000 rev. · NOK −34,000 profit

ABO SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ABO SERVICE AS

Who owns ABO SERVICE AS?

ESPEN ROAR BAKKE is the largest registered owner, with 100.0%.

What is the revenue of ABO SERVICE AS?

ABO SERVICE AS had revenue of NOK 689,000 in 2024.

Who is the general manager of ABO SERVICE AS?

Espen Roar Bakke is registered as general manager of ABO SERVICE AS.

Where is ABO SERVICE AS based?

ABO SERVICE AS has its business address in Stabekk.

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.