BIZTRAC BETA
Rental and leasing of water transport equipment

KEY TANKERS AS

Org. no. 914593085 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 218.2m
Operating profit NOK 58.4m
Equity NOK 147.2m
Incorporated 2014
Employees 6
Share capital NOK 110,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KEY TANKERS AS is registered as a limited company in Bergen, Vestland with organisation number 914593085. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 110,000, divided into 100 shares. The company's stated purpose is: “Investering i og drift av skip samt det som naturlig har sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 218.2m in revenue and NOK 58.4m in operating profit.

Key figures · 2024

Revenue
NOK 218.2m
Operating profit
NOK 58.4m
Equity
NOK 147.2m
Est. value
NOK 274.4m

Financial health · 2024

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

Who owns KEY TANKERS AS?

TANK AS
KEY TANKERS AS
NOK 218.2m rev. · NOK 58.4m profit

KEY TANKERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KEY TANKERS AS

Who owns KEY TANKERS AS?

TANK AS is the largest registered owner, with 100.0%.

What is the revenue of KEY TANKERS AS?

KEY TANKERS AS had revenue of NOK 218.2m in 2024.

Who is the general manager of KEY TANKERS AS?

Sigbjørn Tysse is registered as general manager of KEY TANKERS AS.

Where is KEY TANKERS AS based?

KEY TANKERS AS has its business address in Bergen.

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.