BIZTRAC BETA
Business and other management consultancy activities

JTB HOLDING AS

Org. no. 920367682 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 3.7m
Equity NOK 4.4m
Incorporated 2018
Share capital NOK 30,000

JTB HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 920367682. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Bedriftsrådgivning, konsulenttjenester innen administrasjon, ledelse og kontorarbeid, samt annen virksomhet og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 3.7m
Equity
NOK 4.4m
Est. value
NOK 14.3m

Financial health · 2025

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

Who owns JTB HOLDING AS?

ROBIN VESTNES ROBINSEN
JTB HOLDING AS
NOK 4.1m rev. · NOK 3.7m profit

JTB HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JTB HOLDING AS

Who owns JTB HOLDING AS?

ROBIN VESTNES ROBINSEN is the largest registered owner, with 100.0%.

What is the revenue of JTB HOLDING AS?

JTB HOLDING AS had revenue of NOK 4.1m in 2025.

Where is JTB HOLDING AS based?

JTB HOLDING AS has its business address in Lysaker.

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.