BIZTRAC BETA
Repair and maintenance of machinery

OLJESERVICE AS

Org. no. 924882301 Limited company (AS) Bergen Incorporated 1979 Active
Ownership graph ↗
Revenue 2025 NOK 38.5m
Operating profit NOK 5.9m
Equity NOK 2.9m
Incorporated 1979
Employees 11
Share capital NOK 250,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OLJESERVICE AS is registered as a limited company in Bergen, Vestland with organisation number 924882301. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1979 and has 11 registered employees. Registered share capital is NOK 250,000, divided into 5 shares. The company's stated purpose is: “Servicevirksomhet for oljebransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 38.5m in revenue and NOK 5.9m in operating profit.

Key figures · 2025

Revenue
NOK 38.5m
Operating profit
NOK 5.9m
Equity
NOK 2.9m
Est. value
NOK 20.8m

Financial health · 2025

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

Who owns OLJESERVICE AS?

V HOLDING AS
OLJESERVICE AS
NOK 38.5m rev. · NOK 5.9m profit

OLJESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OLJESERVICE AS er morselskap for 1 datterselskap:

Frequently asked questions about OLJESERVICE AS

Who owns OLJESERVICE AS?

V HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OLJESERVICE AS?

OLJESERVICE AS had revenue of NOK 38.5m in 2025.

Who is the general manager of OLJESERVICE AS?

Viktor Aase is registered as general manager of OLJESERVICE AS.

Where is OLJESERVICE AS based?

OLJESERVICE AS has its business address in Olsvik.

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.