BIZTRAC BETA
Other technical consultancy

PROSESS AUTOMASJON AS

Org. no. 995781611 Limited company (AS) Nord-Aurdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 660,000
Equity NOK 2.5m
Incorporated 2011
Share capital NOK 100,000

PROSESS AUTOMASJON AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 995781611. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg, markedsføring og entreprenørvirksomhet innen prosessindustri, vann, avløp, bygg, anlegg, maskin og enøk, samt ved aksjetegning eller på annen måte gjøre seg interessert i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 660,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 660,000
Equity
NOK 2.5m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns PROSESS AUTOMASJON AS?

EIVIND FOLLINGLO
PROSESS AUTOMASJON AS
NOK 4.6m rev. · NOK 660,000 profit

PROSESS AUTOMASJON AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROSESS AUTOMASJON AS

Who owns PROSESS AUTOMASJON AS?

EIVIND FOLLINGLO is the largest registered owner, with 61.0%.

What is the revenue of PROSESS AUTOMASJON AS?

PROSESS AUTOMASJON AS had revenue of NOK 4.6m in 2024.

Who is the general manager of PROSESS AUTOMASJON AS?

Eivind Follinglo is registered as general manager of PROSESS AUTOMASJON AS.

Where is PROSESS AUTOMASJON AS based?

PROSESS AUTOMASJON AS has its business address in Fagernes.

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.