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

TKBO AS

Org. no. 914989663 Limited company (AS) Sandefjord Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −118,000
Equity NOK 25.2m
Incorporated 2015
Share capital NOK 283,000

Signals

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

TKBO AS is registered as a limited company in Sandefjord, Vestfold with organisation number 914989663. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 283,000, divided into 2 shares. The company's stated purpose is: “Delta i, investere i og drive andre selskaper og sammenslutninger, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −118,000
▲ +68 %
Equity
NOK 25.2m
▼ −0 %
Est. value
NOK 25.7m

Financial health · 2025

Liquidity
33.06
Very good
Current assets ÷ current liabilities
Profitability
11.7%
Good
Return on total assets
Solidity
97.1%
Very good
Equity as a share of total capital

Who owns TKBO AS?

TKBO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TKBO AS own?

TKBO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TKBO AS

Who owns TKBO AS?

KJELL HENRY OLSEN is the largest registered owner, with 50.0%.

Where is TKBO AS based?

TKBO AS has its business address in Sandefjord.

Property

Business address Brygga 11, 3210 Sandefjord
Cadastral unit 3907-173/4/0/0

6 companies are registered at this address.

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.