BIZTRAC BETA
Uoppgitt

DRAMMEN AUTOMASJON AS

Org. no. 915448755 Limited company (AS) Holmestrand Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 184,000
Equity NOK 676,000
Incorporated 2015
Share capital NOK 120,000

DRAMMEN AUTOMASJON AS is registered as a limited company in Holmestrand, Vestfold with organisation number 915448755. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 120,000, divided into 80 shares. The company's stated purpose is: “Eie av aksje og andeler samt handel, eksport, import, konsulentvirksomhet, opplæring og det som naturlig hører inn under dette, herunder deltakelse i andre selskap med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 184,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 184,000
Equity
NOK 676,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns DRAMMEN AUTOMASJON AS?

STEINAR STEVNING HOLE
DRAMMEN AUTOMASJON AS
NOK 1.8m rev. · NOK 184,000 profit

DRAMMEN AUTOMASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRAMMEN AUTOMASJON AS

Who owns DRAMMEN AUTOMASJON AS?

STEINAR STEVNING HOLE is the largest registered owner, with 100.0%.

What is the revenue of DRAMMEN AUTOMASJON AS?

DRAMMEN AUTOMASJON AS had revenue of NOK 1.8m in 2024.

Who is the general manager of DRAMMEN AUTOMASJON AS?

Steinar Stevning Hole is registered as general manager of DRAMMEN AUTOMASJON AS.

Where is DRAMMEN AUTOMASJON AS based?

DRAMMEN AUTOMASJON AS has its business address in Sande I Vestfold.

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.