BIZTRAC BETA
Repair and maintenance of machinery

MOBIL HYDRAULIKK AS

Org. no. 942606249 Limited company (AS) Elverum Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 217,000
Equity NOK 247,000
Incorporated 1986
Share capital NOK 100,000

MOBIL HYDRAULIKK AS is registered as a limited company in Elverum, Innlandet with organisation number 942606249. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Forretningsmessig drift av mekanisk verksted, teknisk konsulentvirksomhet og salg innen transportbransjen samt deltagelse i andre foretak med lignende formål og utlån av ledig kapital.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 217,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 217,000
Equity
NOK 247,000
Est. value
NOK 951,000

Financial health · 2025

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

Who owns MOBIL HYDRAULIKK AS?

BÅRD INGSTAD FLISEN
MOBIL HYDRAULIKK AS
NOK 2.1m rev. · NOK 217,000 profit

MOBIL HYDRAULIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOBIL HYDRAULIKK AS

Who owns MOBIL HYDRAULIKK AS?

BÅRD INGSTAD FLISEN is the largest registered owner, with 100.0%.

What is the revenue of MOBIL HYDRAULIKK AS?

MOBIL HYDRAULIKK AS had revenue of NOK 2.1m in 2025.

Who is the general manager of MOBIL HYDRAULIKK AS?

Bård Ingstad Flisen is registered as general manager of MOBIL HYDRAULIKK AS.

Where is MOBIL HYDRAULIKK AS based?

MOBIL HYDRAULIKK AS has its business address in Elverum.

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.