BIZTRAC BETA
Other technical consultancy

AUTOMASJON SERVICE AS

Org. no. 911627000 Limited company (AS) Øygarden Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 995,000
Equity NOK 107,000
Incorporated 2013
Employees 5
Share capital NOK 30,000

AUTOMASJON SERVICE AS is registered as a limited company in Øygarden, Vestland with organisation number 911627000. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Drive konsulentvirksomhet, herunder rådgivning, kursvirksomhet og opplæring og investere og delta i andre selskaper, samt det som står i forbindelse med de ovennevnte formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 995,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 995,000
Equity
NOK 107,000
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.3%
Weak
Equity as a share of total capital

Who owns AUTOMASJON SERVICE AS?

EIRIK LILLEBØ
AUTOMASJON SERVICE AS
NOK 4.6m rev. · NOK 995,000 profit

AUTOMASJON SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUTOMASJON SERVICE AS

Who owns AUTOMASJON SERVICE AS?

EIRIK LILLEBØ is the largest registered owner, with 100.0%.

What is the revenue of AUTOMASJON SERVICE AS?

AUTOMASJON SERVICE AS had revenue of NOK 4.6m in 2025.

Who is the general manager of AUTOMASJON SERVICE AS?

Eirik Lillebø is registered as general manager of AUTOMASJON SERVICE AS.

Where is AUTOMASJON SERVICE AS based?

AUTOMASJON SERVICE AS has its business address in Straume.

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.