BIZTRAC BETA
Manufacture of other general-purpose machinery n.e.c.

MONGSTAD SERVICE AS

Org. no. 984058144 Limited company (AS) Austrheim Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 15.5m
Operating profit NOK −58,000
Equity NOK 4.9m
Incorporated 2001
Share capital NOK 575,000

Signals

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

MONGSTAD SERVICE AS is registered as a limited company in Austrheim, Vestland with organisation number 984058144. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 2001. Registered share capital is NOK 575,000, divided into 575 shares. The company's stated purpose is: “Utøve salg, service og utleievirksomhet rettet mot industri, anlegg, off.sektor og skip.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.5m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.5m
Operating profit
NOK −58,000
Equity
NOK 4.9m
Est. value
NOK 10.9m

Financial health · 2024

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

Who owns MONGSTAD SERVICE AS?

E HAUGEN AS
MONGSTAD SERVICE AS
NOK 15.5m rev. · NOK −58,000 profit

MONGSTAD SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MONGSTAD SERVICE AS

Who owns MONGSTAD SERVICE AS?

E HAUGEN AS is the largest registered owner, with 91.7%.

What is the revenue of MONGSTAD SERVICE AS?

MONGSTAD SERVICE AS had revenue of NOK 15.5m in 2024.

Who is the general manager of MONGSTAD SERVICE AS?

Enok Harald Haugen is registered as general manager of MONGSTAD SERVICE AS.

Where is MONGSTAD SERVICE AS based?

MONGSTAD SERVICE AS has its business address in Mongstad.

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.