BIZTRAC BETA
Non-scheduled passenger transport by road

JOHAN'S TURBUSS AS

Org. no. 914192501 Limited company (AS) Tønsberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 763,000
Equity NOK 3.0m
Incorporated 2014
Share capital NOK 30,000

JOHAN'S TURBUSS AS is registered as a limited company in Tønsberg, Vestfold with organisation number 914192501. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reise- og turbilformidling med de rettigheter som løyvet (bevillingen) til enhver tid tilsier, samt aksjetegning eller på annen måte gjøre seg interessert i andre foretak innen bransjen, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 763,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 763,000
Equity
NOK 3.0m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns JOHAN'S TURBUSS AS?

JOHAN HASLESTAD
JOHAN'S TURBUSS AS
NOK 4.6m rev. · NOK 763,000 profit

JOHAN'S TURBUSS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOHAN'S TURBUSS AS

Who owns JOHAN'S TURBUSS AS?

JOHAN HASLESTAD is the largest registered owner, with 90.0%.

What is the revenue of JOHAN'S TURBUSS AS?

JOHAN'S TURBUSS AS had revenue of NOK 4.6m in 2025.

Who is the general manager of JOHAN'S TURBUSS AS?

Johan Haslestad is registered as general manager of JOHAN'S TURBUSS AS.

Where is JOHAN'S TURBUSS AS based?

JOHAN'S TURBUSS AS has its business address in Våle.

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.