BIZTRAC BETA
Scheduled passenger transport by road

Tinn Billag AS

Org. no. 916765886 Limited company (AS) Tinn Incorporated 1936 Active
Ownership graph ↗
Revenue 2024 NOK 15.6m
Operating profit NOK 334,000
Equity NOK 27.3m
Incorporated 1936
Share capital NOK 1.0m

Tinn Billag AS is registered as a limited company in Tinn, Telemark with organisation number 916765886. The business is classified under scheduled passenger transport by road (NACE 49.310). The company was incorporated in 1936. Registered share capital is NOK 1.0m. The company's stated purpose is: “Person- og godstransport, verksted og annen virksomhet i naturlig forbindelse med dette, samt eiendomsutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.6m in revenue and NOK 334,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.6m
Operating profit
NOK 334,000
Equity
NOK 27.3m
Est. value
NOK 18.1m

Financial health · 2024

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

Who owns Tinn Billag AS?

TINN KOMMUNE
Tinn Billag AS
NOK 15.6m rev. · NOK 334,000 profit

Tinn Billag AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does Tinn Billag AS own?

Tinn Billag AS holds stakes in 8 companies:

See the full ownership structure →

Group structure

Tinn Billag AS er morselskap for 3 datterselskaper:

Frequently asked questions about Tinn Billag AS

Who owns Tinn Billag AS?

TINN KOMMUNE is the largest registered owner, with 5.5%.

What is the revenue of Tinn Billag AS?

Tinn Billag AS had revenue of NOK 15.6m in 2024.

Who is the general manager of Tinn Billag AS?

Vidar Barlindokk is registered as general manager of Tinn Billag AS.

Where is Tinn Billag AS based?

Tinn Billag AS has its business address in Rjukan.

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.