BIZTRAC BETA
COMPANY REGISTER PROFILE
935465672 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TKT HOLDING AS

Org. no. 935465672 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −92
Equity NOK 235,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−92 kr).

TKT HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 935465672. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eierskap og investering i aksjer og andeler, deltakelse i andre selskaper og virksomheten som hører inn under dette. Investering i og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −92
Equity
NOK 235,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.1%
Good
Equity as a share of total capital

Who owns TKT HOLDING AS?

TKT HOLDING AS
· NOK −92 profit

TKT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TKT HOLDING AS

Who owns TKT HOLDING AS?

THOMAS KARLSEN TJENTLAND is the largest registered owner, with 100.0%.

Where is TKT HOLDING AS based?

TKT HOLDING AS has its business address in Svarstad.

Property

Business address Danmarksveien 9, 3275 Svarstad
Cadastral unit 3909-31/120/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.