BIZTRAC BETA
Retail sale of motor vehicles

AUTO A-67 AS

Org. no. 830823972 Limited company (AS) Tvedestrand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 8.8m
Operating profit NOK −1.3m
Equity NOK 931,000
Incorporated 2023
Employees 5
Share capital NOK 3.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).

AUTO A-67 AS is registered as a limited company in Tvedestrand, Agder with organisation number 830823972. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 3.1m, divided into 3125000 shares. The company's stated purpose is: “Bilverkerksted, samt andre tjenester som naturlig hører inn under dette. Kjøp og salg av biler Selskapet kan eie aksjer/andeler i andre selskaper”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK −1.3m in operating profit.

Key figures · 2025

Revenue
NOK 8.8m
Operating profit
NOK −1.3m
Equity
NOK 931,000
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns AUTO A-67 AS?

GT AUTOMOTIVE HOLDING AS
AUTO A-67 AS
NOK 8.8m rev. · NOK −1.3m profit

AUTO A-67 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AUTO A-67 AS

Who owns AUTO A-67 AS?

GT AUTOMOTIVE HOLDING AS is the largest registered owner, with 52.0%.

What is the revenue of AUTO A-67 AS?

AUTO A-67 AS had revenue of NOK 8.8m in 2025.

Who is the general manager of AUTO A-67 AS?

Tore Vellene Skaaland is registered as general manager of AUTO A-67 AS.

Where is AUTO A-67 AS based?

AUTO A-67 AS has its business address in Tvedestrand.

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.