BIZTRAC BETA
Business and other management consultancy activities

FTL CAPITAL AS

Org. no. 922712271 Limited company (AS) Gjøvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 818,000
Equity NOK 869,000
Incorporated 2019
Share capital NOK 60,000

FTL CAPITAL AS is registered as a limited company in Gjøvik, Innlandet with organisation number 922712271. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder eie aksjer og opsjoner, samt å tilby konsulenttjenester innen bedriftsrådgivning, produktledelse, og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 818,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 818,000
Equity
NOK 869,000
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns FTL CAPITAL AS?

JOHANNES CHRISTIAN KROKEIDE KOLBERG
FTL CAPITAL AS
NOK 2.2m rev. · NOK 818,000 profit

FTL CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FTL CAPITAL AS own?

FTL CAPITAL AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about FTL CAPITAL AS

Who owns FTL CAPITAL AS?

JOHANNES CHRISTIAN KROKEIDE KOLBERG is the largest registered owner, with 100.0%.

What is the revenue of FTL CAPITAL AS?

FTL CAPITAL AS had revenue of NOK 2.2m in 2024.

Where is FTL CAPITAL AS based?

FTL CAPITAL AS has its business address in Gjøvik.

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.