BIZTRAC BETA
Repair and maintenance of motor vehicles

AUTO-TEKNIKK DRØBAK AS

Org. no. 984049560 Limited company (AS) Frogn Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 12.6m
Operating profit NOK 1.1m
Equity NOK 3.8m
Incorporated 2001
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-24 Aksjekapital registrert 2026-02-24.

AUTO-TEKNIKK DRØBAK AS is registered as a limited company in Frogn, Akershus with organisation number 984049560. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2001 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Bilverksted, samt annet inntektsbringende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 12.6m
Operating profit
NOK 1.1m
Equity
NOK 3.8m
Est. value
NOK 6.7m

Financial health · 2024

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

Who owns AUTO-TEKNIKK DRØBAK AS?

KAY BIESENBAUM
AUTO-TEKNIKK DRØBAK AS
NOK 12.6m rev. · NOK 1.1m profit

AUTO-TEKNIKK DRØBAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUTO-TEKNIKK DRØBAK AS

Who owns AUTO-TEKNIKK DRØBAK AS?

KAY BIESENBAUM is the largest registered owner, with 100.0%.

What is the revenue of AUTO-TEKNIKK DRØBAK AS?

AUTO-TEKNIKK DRØBAK AS had revenue of NOK 12.6m in 2024.

Who is the general manager of AUTO-TEKNIKK DRØBAK AS?

Kay Biesenbaum is registered as general manager of AUTO-TEKNIKK DRØBAK AS.

Where is AUTO-TEKNIKK DRØBAK AS based?

AUTO-TEKNIKK DRØBAK AS has its business address in Drøbak.

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.