BIZTRAC BETA
Retail sale of motor vehicles

TOMMY HOLTAN AS

Org. no. 880692062 Limited company (AS) Larvik Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 480,000
Equity NOK −39,000
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−39k kr).

TOMMY HOLTAN AS is registered as a limited company in Larvik, Vestfold with organisation number 880692062. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel med kjøretøyer, båter og mobiltelefonutstyr, samt investering i aksjer og eiendom. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 480,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 480,000
Equity
NOK −39,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TOMMY HOLTAN AS?

TOMMY BØE HOLTAN
TOMMY HOLTAN AS
NOK 1.4m rev. · NOK 480,000 profit

TOMMY HOLTAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOMMY HOLTAN AS

Who owns TOMMY HOLTAN AS?

TOMMY BØE HOLTAN is the largest registered owner, with 100.0%.

What is the revenue of TOMMY HOLTAN AS?

TOMMY HOLTAN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of TOMMY HOLTAN AS?

Tommy Bøe Holtan is registered as general manager of TOMMY HOLTAN AS.

Where is TOMMY HOLTAN AS based?

TOMMY HOLTAN AS has its business address in Larvik.

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.