BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

ENGER AGRISERVICE AS

Org. no. 997302664 Limited company (AS) Indre Østfold Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 11.2m
Operating profit NOK −58,000
Equity NOK 446,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

ENGER AGRISERVICE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 997302664. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg og vedlikehold av utstyr til melkeproduksjon.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.2m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.2m
Operating profit
NOK −58,000
Equity
NOK 446,000
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns ENGER AGRISERVICE AS?

EIRIK ENGER
ENGER AGRISERVICE AS
NOK 11.2m rev. · NOK −58,000 profit

ENGER AGRISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENGER AGRISERVICE AS

Who owns ENGER AGRISERVICE AS?

EIRIK ENGER is the largest registered owner, with 100.0%.

What is the revenue of ENGER AGRISERVICE AS?

ENGER AGRISERVICE AS had revenue of NOK 11.2m in 2024.

Who is the general manager of ENGER AGRISERVICE AS?

Eirik Enger is registered as general manager of ENGER AGRISERVICE AS.

Where is ENGER AGRISERVICE AS based?

ENGER AGRISERVICE AS has its business address in Båstad.

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.