BIZTRAC BETA
Other tour operator activities

TELEMARK TRAVEL AS

Org. no. 916175841 Limited company (AS) Notodden Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 320,000
Equity NOK 856,000
Incorporated 2015
Share capital NOK 30,000

TELEMARK TRAVEL AS is registered as a limited company in Notodden, Telemark with organisation number 916175841. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Informasjon om, pakketering av, salg og gjennomføring av opplevelser med utgangspunkt i industriell verdensarv, regional historie, kultur og natur. I tillegg annen type virksomhet som bidrar til steds-/næringsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 320,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 320,000
Equity
NOK 856,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns TELEMARK TRAVEL AS?

HANS-OTTO KASIN
TELEMARK TRAVEL AS
NOK 1.0m rev. · NOK 320,000 profit

TELEMARK TRAVEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TELEMARK TRAVEL AS

Who owns TELEMARK TRAVEL AS?

HANS-OTTO KASIN is the largest registered owner, with 100.0%.

What is the revenue of TELEMARK TRAVEL AS?

TELEMARK TRAVEL AS had revenue of NOK 1.0m in 2025.

Who is the general manager of TELEMARK TRAVEL AS?

Hans-Otto Kasin is registered as general manager of TELEMARK TRAVEL AS.

Where is TELEMARK TRAVEL AS based?

TELEMARK TRAVEL AS has its business address in Notodden.

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.